5650bf33fa
The wrapper for "git blame" creates flags for each line of the buffer. It parses the output from git and would send a flag (or a series of flags) each time the commit to blame for a line differs from the previous one. For files that were touched by a large number of commits, this results in a high number of kakoune processes being launched, and may take some time. This is visible in the session through the flags for the different commits appearing on the lines one by one, possibly during several seconds. To speed up the process, batch flags before passing them to the kak session. One solution could be to send all flags at once, but this might delay the appearance of commit info for too long if "git blame" really takes a long time. The alternative solution retained for this commit consists in grouping as many flags as we can during one second (roughly), to pass them to kakoune, and then to move on to the next flags. This way, a new batch of commit information flags appears every second or so in the client, until all information is added. This should be much faster than lauching a kakoune process for each commit reported by "git blame": tests have shown that blaming a large file in the Linux repository goes 4.5 times faster when batching flags. Co-authored-by: Johannes Altmanninger <aclopte@gmail.com> |
||
---|---|---|
.. | ||
go | ||
python | ||
rust | ||
autorestore.asciidoc | ||
autorestore.kak | ||
autowrap.kak | ||
clang.kak | ||
comment.kak | ||
ctags.kak | ||
doc.asciidoc | ||
doc.kak | ||
format.kak | ||
git.kak | ||
grep.kak | ||
lint.asciidoc | ||
lint.kak | ||
make.kak | ||
man.kak | ||
spell.kak |