Johannes Altmanninger
Johannes Altmanninger
On Tue, Jun 13, 2023 at 10:45:05AM -0700, Matthieu Talbot wrote: > In `tig`, executing `:!git commit --amend` tries to call EDITOR, in my case vim, but fails, displaying >...
you can set TIG_SCRIPT to execute arbitrary commands at startup
> , shows the last commit before the blamed commit for the current line that modified the selected line. Right. I never really used, it seems nice. Sadly it can't...
I remember having similar problems on Ubuntu 16, without custom CFLAGS. I worked around it by disabling PCRE support.. Perhaps it's an incompatiblity with old libpcre2
Tig doesn't have dedicated support for this feature yet; I think it would be a nice feature. In the diff view, pressing `u` could add the selected hunk to a...
@mqudsi No idea what's the cause of this issue but it's nice that you're also using Tig :) I use it for all my code archaeology and code review needs....
yes it's https://github.com/mawww/kakoune/issues/4975 there is some more commentary but no conclusion on https://github.com/mawww/kakoune/pull/4994
It looks like the point of vim's `completeopt = noinsert` is to make the first `` only show the menu but not insert the first candidate. Kakoune provides autocompletion, so...
I think it's possible we could improve the default UI here (change behavior of `` and `` to undo and accept). But I'm not sure if the case for ``...
> The inherent problem there is that it can't use the ts_tree_edit API efficiently to make reparsing of large buffers cheap instead reparsing the entire buffer sent over a pipe...