Sergey Vlasov
Sergey Vlasov
Sorry to invade the thread, but you cannot run vim functions in the background and async-run plugin is not helping there. However what is possible in theory is fire up...
Using `job_start()` is the best solution in this case but `s:run_system()` will have to be split into two calls. Before: ```vim silent let ctags_output = s:run_system(a:ctags_cmd, py_version) ``` After: ```vim...
Also a custom key bind to abort please. ^C is a bit hassle.
Sure, I can help. Maybe I could provide a proof-of-concept PR to illustrate the idea.
> What is the declared `ft` for vim9script? `vim` > Does it allow mixing and mating of old style vimL comments in the same file? If the first line is...
They can be distinguished by `commentstring`. New style is `#%s`, old one is `"%s`.
@Cimbali I tried the patch and it mostly works great. However there is a problem with very long lines. Try `seq 1000 | paste -sd+` several times, go to normal...
``` vim -g --clean +'set lines=20 columns=22' +'term bash --noprofile --norc' +'only' ``` then ``` seq 100 | paste -sd+ tput setab 1; echo "this is red text"; tput sgr0...
This was implemented in 07ea5f150.
osxcross is just a toolchain. What it has to do with creating dmg?