This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-17
Channels
- # aws (10)
- # beginners (64)
- # boot (3)
- # cider (20)
- # cljs-dev (32)
- # cljsrn (6)
- # clojure (126)
- # clojure-dusseldorf (3)
- # clojure-finland (1)
- # clojure-greece (1)
- # clojure-italy (7)
- # clojure-poland (3)
- # clojure-spec (46)
- # clojure-uk (100)
- # clojurescript (37)
- # cursive (11)
- # datomic (6)
- # defnpodcast (2)
- # emacs (1)
- # events (3)
- # figwheel (2)
- # fulcro (20)
- # immutant (2)
- # jobs (1)
- # jobs-discuss (9)
- # keechma (3)
- # lein-figwheel (1)
- # luminus (2)
- # lumo (3)
- # mount (2)
- # off-topic (19)
- # om (3)
- # om-next (2)
- # onyx (20)
- # other-languages (55)
- # parinfer (11)
- # pedestal (8)
- # portkey (3)
- # protorepl (3)
- # re-frame (22)
- # ring (9)
- # rum (1)
- # shadow-cljs (82)
- # spacemacs (28)
- # sql (15)
- # test-check (15)
- # testing (2)
- # tools-deps (102)
- # vim (26)
@snoe Did you ever figure out more stuff about :undojoin
? I googled and came across your StackOverflow questions (with no answers) 😄
Specifically, always calling it is bad, since calling it after an undo or redo destroys the undo history. But I haven't been able to figure out how to determine when not to call it.
IIRC I feel that I ran into a wall with it, I don't think it was possible to do what I wanted.
There's a way to get the current undo history. But it seems to indicate our current position incorrectly anyway.
yeah I was looking forward to the nvim api delta events but that seemed to be stuck in it's own quagmire
I cannot imagine what the nvim people must do to add something like that. It's like, "first, read all the code. Then document the 300 cases we need to change to produce a consistent API."
I was poking at Vim and Neovim's job control stuff and channels, and it seems like it should be possible to do the async nrepl stuff without python for both. @dominicm
Opening a socket and communicating asynchronously. I mean, it's kind of what async.vim does.
Vim8 prefers JSON and Neovim prefers msgpack, but both indicate you can do raw if you want.
Heh. Would you accept one if I did it? I'm not sure if I'm serious yet, just checking.
If you can prove it works, sure. Having taken mine through a lot of failure cases now, that would be important. I just got generative testing working and I'm finally quite happy that the exceptions have stopped. We should be careful to look at the performance impact too, but we could always have a fallback approach.
@snoe re: delta events, you mean the thing that’s supposed to notify the consumer of incremental changes to a buffer?
@jebberjeb maybe? It's been over a year since I looked seriously. But like @eraserhd said there's so many ways a buffer can change in vim and the more accurately you can inform parinfer, the better.
I’m really hoping that will be the way to find out without polling. I guess if you listen to redraw
events, and you set the ext-options
map to exclude menu, command line, etc from that, you know something visible on the screen that you might care about changed.