This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (8)
- # beginners (1)
- # boot (127)
- # cider (17)
- # cljs-dev (17)
- # clojure (69)
- # clojure-argentina (3)
- # clojure-australia (35)
- # clojure-japan (1)
- # clojurescript (66)
- # core-matrix (2)
- # cursive (33)
- # datascript (1)
- # emacs (2)
- # hoplon (17)
- # instaparse (1)
- # melbourne (1)
- # off-topic (13)
- # re-frame (7)
- # reagent (3)
@meow: You’re right, the template text is wrong - you can see it in Settings->Editor->Live Templates
Feature suggestion: Scan the doc string of the function for any keyword occurence and suggest/autocomplete them when entering
: somewhere when calling the function
Note that Cursive should autocomplete keywords that have been seen anywhere in the project anyway, so most likely you have an example somewhere.
Although I’ve found that when I first create an example it often takes a while to update the indexes the first time.
Yes the autocomplete is very very useful. I have just noticed it how it magically suggested
:hierarchy (which I always misspell)
Autocompleting strings in general would be super nice. We do some interop with AWS libs, and they use a lot of maps that are string->string. We decided to use their string->string format when we make our calls (as opposed to mapping keywords to strings in our wrappers), and the only regret I have about it is the fact that I don’t get autocomplete on keys of the map in cursive.
@potetm: How would Cursive know what the autocompletions of those strings should be?
We use the same maps over and over pretty much. Just change the right hand side of the map occasionally.
The problem with that is that there are lots of strings in the project that you might not want that for.
I think you want the symbol-looking string thing, because then it’ll work for assoc etc