This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-01-15
Channels
- # announcements (7)
- # aws (30)
- # beginners (141)
- # boot-dev (3)
- # cider (48)
- # clara (35)
- # clojure (94)
- # clojure-europe (6)
- # clojure-italy (20)
- # clojure-nl (19)
- # clojure-norway (1)
- # clojure-portugal (6)
- # clojure-spec (7)
- # clojure-survey (3)
- # clojure-uk (93)
- # clojuredesign-podcast (22)
- # clojurescript (20)
- # core-async (54)
- # cursive (29)
- # datascript (1)
- # datomic (4)
- # emacs (2)
- # fulcro (10)
- # jobs (17)
- # juxt (3)
- # kaocha (20)
- # leiningen (20)
- # malli (22)
- # other-languages (7)
- # pedestal (4)
- # perun (2)
- # quil (2)
- # re-frame (7)
- # reagent (3)
- # reitit (31)
- # shadow-cljs (18)
- # spacemacs (11)
- # vim (32)
i think i may have caught a regression around the behavior of gg
in neovim.
question for vim and neovim users alike:
if you go to an arbitrary line in a file, go to a column > 1, and press gg
, where does your cursor land on line 1?
does it land at line 1, column 1, or does it land on line 1 at the same column where you were?
i upgraded this morning to 0.5.0+ubuntu1+git202001142018-3d1531a-00e710e-8b2f2dc~ubuntu16.04.1, and that's when i noticed the change in behavior
the fact that you're landing on line 1 column 1 on a slightly older version is a great sanity check! 😄
i ruled out it being related out to my vim config by running vim -u NONE
-- still landed on line 1, column != 1
i've filed an issue with neovim https://github.com/neovim/neovim/issues/11719
i think it's my only contribution to neovim thus far, but hopefully it will save somebody a headache 🙂
i wonder if maybe neovim used to default that to true, then recently changed the default to false
@dominicm Hi , what replant#ui#refresh() does ? When I execute I should see the equivalent output of a reset on repl right ?
It will attempt to find a stop function, call tns/refresh, then call a go/start function.
aha -- looks like the default did change from on to off in neovim last month: https://github.com/neovim/neovim/commit/3aa95ef27eb8817bc2ceddb6caf2b209e00a5e8d
interesting to read through the things they turned (and did not turn) on by default: 1. https://github.com/neovim/neovim/issues/2676 (previous list, now completed) 2. https://github.com/neovim/neovim/issues/6289 (continuation list, in progress)
every time i think neovim might be settling down into something usable they pull some bs like this
in general, if you're trying to make a drop-in replacement for something, you should avoid having your thing act differently whenever you can help it
when i was evaluating neovim, i was able to use my vimrc as-is (plugins and all) and it appeared to behave exactly the same, and that's one of the reasons that i chose to switch to neovim
i just think it's weird someone would think the jump to top of file command should preserve column
i jotted down some steps for getting vim-iced to work (from scratch) with neovim and a socket repl:
https://gist.github.com/sogaiu/268a331ddf294db3ed8796c8ee36c758
this includes a small plug for alc.start-repl
-- a cmd line tool for starting socket repls after a clojure process has started :)
@liquidz.uo there were a few things i had to do that i didn't find at: https://liquidz.github.io/vim-iced/
1. i didn't see any mention of :PlugInstall
during the installation of vim-plug. if that is missing, may be it's a nice addition for the not-so-experienced?
2. i got some error about needing to add set hidden
to an initialization file, and i didn't find this in the setup instructions. adding it seemed to fix things.
in any case, thanks for adding some socket repl support!