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?

line 1 column 1, version: v0.5.0-dev (git201909172023)

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 knew i remembered it working that way

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

wow, very nuanced, nice catch!

i think it's my only contribution to neovim thus far, but hopefully it will save somebody a headache 🙂

:h 'startofline'

i don't think i've ever had that set in my vimrc

i wonder if maybe neovim used to default that to true, then recently changed the default to false

what is the default in vim?

@dominicm Hi , what replant#ui#refresh() does ? When I execute I should see the equivalent output of a reset on repl right ?

vim default is on

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

my god, even 'hidden' is up for consideration

yeah, i'm fairly unhappy about this, because it breaks plugins

including my plugin 🙂

i mean, it was a trivial fix - i changed an instance of gg to gg0 - but still

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

whispers plugins should be able to handle non-default options

ok, yes. fair. good point 🙂

i just think it's weird someone would think the jump to top of file command should preserve column

'nostartofline' affects like 20 things and maybe 3 of them are improvements

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!

@sogaiu Cool! Thank you very much! I'll add them to documents!