This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-21
Channels
- # admin-announcements (2)
- # beginners (22)
- # boot (223)
- # cider (161)
- # cljs-dev (19)
- # cljsrn (4)
- # clojure (186)
- # clojure-austin (6)
- # clojure-beijing (1)
- # clojure-boston (3)
- # clojure-china (1)
- # clojure-czech (1)
- # clojure-france (1)
- # clojure-greece (10)
- # clojure-russia (17)
- # clojure-uk (154)
- # clojurebridge (3)
- # clojurescript (82)
- # component (12)
- # cursive (12)
- # datomic (71)
- # dirac (3)
- # editors (2)
- # emacs (29)
- # flambo (31)
- # hoplon (21)
- # immutant (11)
- # instaparse (17)
- # jobs (2)
- # jobs-discuss (2)
- # jobs-rus (1)
- # lein-figwheel (12)
- # leiningen (2)
- # off-topic (44)
- # om (78)
- # onyx (38)
- # parinfer (1)
- # re-frame (34)
- # reagent (32)
- # spacemacs (56)
- # untangled (74)
- # vim (12)
- # yada (2)
@udit: are you still having issues? If so can you tell me which version of clojure is specified in your boot/project file?
I have to type the entire package name in order to get autocompletion, like java.util.UUID
If I understand this correctly, it should: http://bytopia.org/2015/03/06/smart-classname-completion-for/
Hmm, I must have broken my configuration. When I start cider (0.12) I see this in REPL:
WARNING: CIDER's version (0.12.0) does not match cider-nrepl's version (nil). Things will break!
WARNING: The following nREPL ops are not supported:
artifact-list artifact-versions clean-ns extract-definition find-symbol find-used-locals hotload-dependency namespace-aliases rename-file-or-dir resolve-missing stubs-for-interface version warm-ast-cache
Please, install (or update) refactor-nrepl and restart the REPL.
You can mute this warning by changing cljr-suppress-middleware-warnings.
WARNING: clj-refactor and refactor-nrepl are out of sync.
Their versions are 2.0.0-SNAPSHOT (package: 20151210.200) and n/a, respectively.
You can mute this warning by changing cljr-suppress-middleware-warnings.
user>
In Messages buffer everything looks ok:
Starting nREPL server via lein update-in :dependencies conj \[org.clojure/tools.nrepl\ \"0.2.12\"\] -- update-in :plugins conj \[cider/cider-nrepl\ \"0.12.0\"\] -- repl :headless…
The support was dropped since cljs requires 1.7.0 and above and they didn't want to manage the different versions
@jstaffans: yes. Completion works for java classes. However, you probably need to type more than two characters to trigger your completion menu.
@malabarba: you mean start from the start of the class name?
hmm.. I type ConcurrentLi<TAB>
and get No matches
. I have to start typing from the start of the package name to see the completion menu: java.util.concurrent.ConcurrentLi<TAB>
Also j.u.c.ConcurrentLi
does’t work … what other packages does this completion depend on? I’m thinking the clojure layer in Spacemacs is broken somehow ..
@malabarba: company doesn’t support this
@bozhidar: are you referring to getting completion without typing the start of the symbol?
original thread - https://github.com/company-mode/company-mode/issues/47
you put up a feature request on cider to remember which build version you used for cider
i was thinking remember across sessions might be difficult, but is it asking you which to use each time you redo it in the same session of emacs?
It does ask each time. I occasionally have to kill my repl to flush bugged datomic state.
seems like it might be pretty easy to keep a project-buildtype keyvalue to just remember the last one you entered
Though, I realize that only makes sense for my case of 100% of the time wanting to start all projects with lein.
my thinking was to make you choose the first time and remember that for all successive jack-ins
and i think malabarba mentioned you could c-u c-c m-j to force it to ignore the cache
I do things like this in my .emacs:
(setq grep-find-ignored-directories '(".git" "out" ...
so if I could setq some state so cider would know I always wanted to start project X w/ lein.....
I personally like managing state that way, because my .emacs is in source control, and I can avoid the AUTO-CONFIG var puke...
i'll research if there is a way to persist things in packages that survive updates, don't encroach on the users files, etc, that we can remember an initial choice
wonder if there's something to the ordering: 1) allow explicit overrides 2) allow general resolution strategy of multiple builds 3) remember last choice during same session and offer to persist this choice
i'll look into the cider dict structure. Probably is a default value, which could be user set
yeah. i thought i remembered a package had done it somewhere else but i can't remember which one
I think we can start by adding a variable that lets people choose the default. We don't need to save anyuthing yet
oh is there no canonical name for the project? something cider would use as the name?
while projects do have names, CIDER doesn't know how to figure that out, and I'd rather not teach it
By default the variable will be nil, and whenever the current directory is not in the variable we just ask like we currently do
i was thinking allow for a custom set variable that would give a resolution strategy, so that when there are multiple bulid chains, like harold has, it would be able to just globablly prefer one or the other if the project doesn't have one explicitly set?
There are already plenty of cider options that users may need to change on all per-project basis
what's a good variable name that says cider will use this when there are multiple possible build systems
will most people use a string "lein", is it convention that i can set my type or should i be preparred for (setq cider-default-commands 'lein)
I'd rather give an explicit error if the user made that mistake, than try to account for it and complicate the code
Of course, regardless of anything else you should always list the possible values in the docstring of the variable.