This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-08-28
Channels
- # bangalore-clj (1)
- # beginners (67)
- # braveandtrue (179)
- # cider (28)
- # cljdoc (1)
- # clojure (132)
- # clojure-conj (3)
- # clojure-dev (1)
- # clojure-finland (6)
- # clojure-nl (2)
- # clojure-russia (6)
- # clojure-spec (19)
- # clojure-uk (62)
- # clojurescript (90)
- # clojutre (5)
- # component (2)
- # cursive (30)
- # data-science (1)
- # datomic (42)
- # duct (9)
- # emacs (1)
- # figwheel-main (158)
- # fulcro (57)
- # funcool (3)
- # hoplon (1)
- # jobs (17)
- # mount (38)
- # off-topic (15)
- # re-frame (53)
- # remote-jobs (2)
- # schema (11)
- # shadow-cljs (299)
- # spacemacs (25)
- # specter (2)
- # tools-deps (54)
- # vim (11)
- # yada (6)
I have just discovered the kakoune editor, and I am enamored. This will likely end badly. https://github.com/mawww/kakoune
I mean, it really seems to be "vim done better" and the design choices are kind of amazing. I'm worried about ergonomics a bit.
One thing for sure, though, the idea that tmux should be the thing controlling the panes seems good to me. I think I'm going to do that. I can't really think of what I'd lose, except for minor things that can be fixed.
The only other thing I can think of as a drawback is that auto-complete cannot be wider than the buffer.
It seems to be client/server so that state would be shared between windows?
@clashthebunny at this point, I only have a vague sense of how it works, but I think each instance is a server.
I guess each server is named. Check out how they focus a pane 😄 https://github.com/mawww/kakoune/blob/master/rc/base/tmux.kak#L41-L50