@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

+1 from me too

@rauh: Can you file an issue for that so it doesn’t get lost?

Will do

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)

Heh nice

It does some nice things with namespaced keywords too

https://github.com/cursiveclojure/cursive/issues/1043

Thanks.

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.

http://img2.wikia.nocookie.net/__cb20140304223324/glee/images/2/2c/Sad_panda.jpg

@potetm: How would Cursive know what the autocompletions of those strings should be?

From the doc, or something?

Other usages, same as keywords.

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.

Perhaps I could index strings which only have a symbol-looking thing inside them.

True story. Maybe just for strings in literals?

Or that, yeah.

And then only offer completions for strings where that is true.

strings in collection literals, that is

I think you want the symbol-looking string thing, because then it’ll work for assoc etc

Yeah, that would be perfect. Sounds hard to me, but that’s pretty much what I want.

Right.

Good call.

Issue please

10 4

https://github.com/cursiveclojure/cursive/issues/1046

Nice, thanks!

My pleasure. Thank you!