This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-19
Channels
- # beginners (69)
- # boot (10)
- # cider (18)
- # cljsrn (6)
- # clojure (225)
- # clojure-austin (1)
- # clojure-dusseldorf (7)
- # clojure-france (2)
- # clojure-greece (3)
- # clojure-italy (9)
- # clojure-madison (6)
- # clojure-miami (1)
- # clojure-mke (2)
- # clojure-russia (58)
- # clojure-sg (36)
- # clojure-spec (25)
- # clojure-uk (54)
- # clojurescript (20)
- # core-async (15)
- # cursive (16)
- # datomic (71)
- # emacs (7)
- # hoplon (3)
- # jobs (5)
- # jobs-discuss (4)
- # klipse (3)
- # leiningen (2)
- # lumo (60)
- # mount (1)
- # off-topic (16)
- # om (6)
- # om-next (7)
- # onyx (21)
- # pedestal (15)
- # planck (1)
- # re-frame (3)
- # ring-swagger (4)
- # specter (33)
- # uncomplicate (31)
- # untangled (8)
- # vim (35)
I have a weird problem. When I switch from one file to another, the keyboard shortcuts for some actions appear to apply to the file I am no longer looking at.
I’ve tried ‘select all’ and ‘cycle collection type’ and they both apply to the no-longer-visible file.
@peterwestmacott I’ve never seen anything like that. Does it happen with other languages too? It sounds like an IntelliJ level problem.
yeah, that’s what I suspect
it is properly weird
I’ve noticed it a few times since the 2017.1 update to IntelliJ
I’m only really writing Clojure at the moment (:-D) so I’ve not noticed it elsewhere
it seems like some level of “focus” gets stuck on one file, and whatever other file I switch to, certain editor actions get sent back to the stuck file.
it’s more surprising than problematic
everything appears normal
but some commands appear to be sent to a different file
it seems to be pretty fundamental to the editor - thanks for thinking about it - keep up the good work!