This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-12
Channels
- # aleph (10)
- # beginners (62)
- # boot (12)
- # cider (97)
- # cljs-dev (171)
- # clojars (1)
- # clojure (224)
- # clojure-italy (4)
- # clojure-nl (2)
- # clojure-russia (1)
- # clojure-spec (41)
- # clojure-uk (68)
- # clojured (7)
- # clojurescript (115)
- # community-development (4)
- # cursive (2)
- # data-science (1)
- # datomic (18)
- # duct (40)
- # emacs (1)
- # events (1)
- # fulcro (148)
- # funcool (2)
- # graphql (2)
- # immutant (3)
- # jobs (3)
- # keechma (1)
- # luminus (2)
- # numerical-computing (1)
- # off-topic (19)
- # om (6)
- # parinfer (10)
- # pedestal (15)
- # precept (86)
- # reagent (12)
- # ring (3)
- # ring-swagger (2)
- # shadow-cljs (42)
- # spacemacs (19)
- # specter (17)
- # sql (11)
- # tools-deps (78)
- # unrepl (62)
- # vim (28)
I wonder if I should try a graphical neovim. The :terminal is handy for repl, but I'm getting somewhat tired of having two layers of tiles and two different bindings to move between them (i3 and neovim)
I'm assuming that I could have the :terminal "split" in a completely new window, of course
@jebberjeb Back from sick leave, thanks for the testing snippet
@tomi.hukkalainen_slac why not just use i3 for everything?
i think one of my coworkers does that. he has a chrome plugin installed that makes new tabs open as new windows
by "use i3 for everything," i mean only use vim for editing single buffers, and if you need to open a split, just open a new window editing the file you want to edit
i guess that approach would take a little bit of setup, but maybe not terrible. i'm imagining writing a vim ex command like :I3edit some-file.foo
and have it shell out to run whatever command you need to do that opens an i3 window with vim /path/to/some-file.foo
That's what I meant by using a graphical neovim; I could have multiple buffers in separate windows
@tomi.hukkalainen_slac what I’ll do some of the time is run my process separately, and launch it with a SocketREPL (using JVM command line args), then in :terminal I’ll do nc localhost port
.
Not sure if that’s useful for your setup, but at least it decouples my Clojure process from Neovim — when I need it
@dominicm You mean running it in multiple terminal emulators, while still in the same process?
Or do you mean that the graphical frontends cannot handle multiple windows either, currently?
Yeah. Neovim has slowed a little. I think they're bug fixing primarily for next release. Less of a feature focus.
Neovim fixes and a new release sounds great for me. I'm running dev build for some features (maybe...) and for last few days it has segfaulted every 10 minutes or so 😕
Apparently there's now socket jobs which aren't rpc based now. Great for the socket repl!
https://neovim.io/doc/user/api.html#nvim_parse_expression() when did this land?!
Neovim fixes and a new release sounds great for me. I'm running dev build for some features (maybe...) and for last few days it has segfaulted every 10 minutes or so 😕