Benoit de Chezelles
Benoit de Chezelles
In my opinion, the best move would be to use `git diff`'s output to build the visualization yourself. The blocker I think is that AFAIK neovim does not have apis...
Sure but people coming on gitter/irc uses this playground to show their ideas and more importantly their errors. And when we try to help someone with an error we might...
Hello, just discovered this nice tool! Is it still blocked? 🙄
You closed this, does that mean the issue is resolved?
FWIW An alternative I use is: ``` #command \e\e quit #line-edit \e\e abort ``` Bind Escape-Escape to quit, and Escape-Escape to abort line editing (to cancel a search for example)....
You can do it without the plugin in the meantime, here is what I do: https://github.com/bew/dotfiles/blob/07d44f841d2f6ea9932754f44bd52e0623cde3ea/nvim/init.vim#L309-L311 ```vim " Add colors to 'arg=' in 'func_call(arg=1)' autocmd FileType python syn match pythonFunctionCallKwargs...
I've read #31 but I think it's different, there is no highlight in my case, and when something is highlighted there is no offset problem (unless it's in a multiline...
Oh that was you! Nice 👍✨ I think it's a good idea to keep existing behavior so the plugin can still be used on systems with old version of git...
note: a workaround might be to not use Alt as the main key for altdrag, but the windows key (which is usually less used)
I don't need that anymore, should I leave this issue open?