This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-12-15
Channels
- # admin-announcements (60)
- # adventofcode (37)
- # beginners (53)
- # boot (94)
- # bristol-clojurians (1)
- # cider (21)
- # clara (19)
- # cljsrn (1)
- # clojure (222)
- # clojure-chicago (1)
- # clojure-dev (2)
- # clojure-nl (11)
- # clojure-russia (301)
- # clojure-turkiye (1)
- # clojurecup (6)
- # clojurescript (30)
- # core-async (3)
- # cursive (64)
- # datascript (2)
- # datomic (55)
- # devops (16)
- # editors (1)
- # emacs (16)
- # ldnclj (6)
- # off-topic (18)
- # om (113)
- # onyx (3)
- # parinfer (1)
- # proton (48)
- # re-frame (20)
- # reagent (7)
it seems like vim mode plus has a lot more stuff than vim-mode. We can always swap it out later again
We need to somehow get the space key on non-editor windows working. I think that might be one of the most important parts
hm so when we bind body or atom-workspace, it would also catch keybindings in insert-mode, which we don't want
so: 1. change logic to append proton-mode class to body / workspace instead 2. make sure the proton:chain triggers correctly 3. make sure it doesn't trigger in text fields and insert mode
It keeps looking like I’m in visual mode, but it doesn’t recognize it. So when I hit escape nothing happens. The only way I have been able to escape it is to reload the editor window
it has a lot more features than vim mode. Stuff like
- block selection (ctrl+v)
- feedback on copy
- instant search results when hitting /
(vim mode wants you to hit enter first)
- incremental search
- smartcases
I’m excited about this, once it is ready: https://github.com/carlosdcastillo/vim-mode
I haven’t been paying enough attention to what I’m doing to figure out what triggers it
I’d like that for the time being. Would that make the other config vars you set harder to work with?
I'll focus on the space everywhere stuff first though. At least when I have some more time