This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-07
Channels
- # adventofcode (269)
- # beginners (100)
- # boot (6)
- # cider (4)
- # cljsrn (4)
- # clojure (161)
- # clojure-android (31)
- # clojure-argentina (2)
- # clojure-brasil (8)
- # clojure-greece (45)
- # clojure-india (2)
- # clojure-madison (2)
- # clojure-russia (17)
- # clojure-spec (4)
- # clojure-sweden (1)
- # clojure-uk (32)
- # clojurescript (93)
- # core-logic (2)
- # cursive (21)
- # data-science (2)
- # datomic (46)
- # defnpodcast (1)
- # duct (5)
- # emacs (21)
- # events (1)
- # fulcro (17)
- # graphql (13)
- # job (1)
- # jobs (2)
- # leiningen (11)
- # lumo (3)
- # off-topic (119)
- # om (4)
- # onyx (2)
- # planck (6)
- # portkey (12)
- # re-frame (5)
- # reagent (3)
- # ring (5)
- # shadow-cljs (27)
- # spacemacs (19)
- # specter (6)
- # unrepl (9)
I'm having trouble with ctrl+up/down moving between functions. I see the Navigation menu lit up as if I've triggered an action within it, but the system bell sounds and the cursor doesn't move.
Looking through the webdocs, it looks like the keybinding docs may be out of date with recent versions of IntelliJ. With IntelliJ IDEA 2017.2.5 on Mac OS X, there's no Clojure option under Preferences > Keymap, and the dialog doesn't look anything like what's on the page. https://cursive-ide.com/userguide/keybindings.html As I'm pretty new to IntelliJ, I might be completely looking in the wrong location.
Thanks.
I am pretty sure the ctrl+up/down keys are the "right" ones, since the menu shows those as the accelerators, and the menu activates when I hit them
I just tried and ascertained that I can manually click those entries in the menu and it works.
I forgot to mention I'm using IdeaVim. I'll try without it.
I did find the Keymap part of settings
preferences
Yeah, it works without the Vim emulation. And I can set a secondary set of keys that do work with the Vim emulation.
And the same is true in a Java project with no Clojure
So I'll take this issue to JetBrains
thanks
@cfleming Thank you for the work-around, and that was an incredibly fast fix on their side. Everything is working smoothly now.
@grzm Yes, that doc is out of date, that was fixed in the latest release. I’ll update the doc shortly.
Hopefully all the keys you need should be bound out of the box now, let me know if you’re missing anything.
I find the "extract variable" refactoring very useful but am I missing an "extract to function" refactoring?
today I updated Cursive and now I can do "jump to definition" on namespace-qualified keywords! nice