Bram Moolenaar
Bram Moolenaar
> > Might be worth adding a link to this help tag at :help 'autoshelldir'. > > How about this patch: Hmm, this is at 'autoshelldir', but it doesn't use...
> OK, this patch is simpler, does assume that `'autoshelldir'` is set, > and explains how to set up the shell: Thanks. I can include this and the other one...
Daniel Hahler wrote: > ```vim > call ch_logfile('/tmp/job.log') > > let g:lines = [] > > function Out_cb(channel, data) > echom "CALLBACK" string(a:channel) string(a:data) > sleep 200m > echom "\n"...
Not sure why you would use a shell command to call a function to open netrw. I don't think that is supposed to work. For me I can use CTRL-C...
> I use vim as a terminal multiplexer, and it's convenient if `vim > ` on the inner terminal doesn't open a nested vim.. I do not encourage using Vim...
Doug Kearns wrote: > The `yamlFlowMappingKey` syntax group is the culprit. It would appear > that the maintainer is aware of this as the pattern specifically > selects the old...
Instead of using getchar(), it's better to have the callback store the result in a variable, and check that variable in the wait loop. Then using the cursor to select...
One of the tests is failing: Found errors in Test_GUI_lowlvl_QWERTY_Ctrl_minus_Ex(): 7981 command line..script D:/a/vim/vim/src/testdir/runtest.vim[468]..function RunTheTest[44]..Test_GUI_lowlvl_QWERTY_Ctrl_minus_Ex[47]..SwapExists Autocommands for "*"..function HandleSwapExists line 10: Unexpected swap file: .Xresult.swp
When writing a file Vim checks that there isn't a swap file for it, to avoid overwriting a file that's being edited in another Vim instance.