Patch bugs neatvi
kyx0r opened this issue · comments
More info here:
aligrudi/neatvi#16
This is due to possibly how the history is handled in tresize() but definitely regression is there.
For now I will refrain from using this.
*tested with upstream clean neatvi build & clean st build + st-vimBrowse-latestRelease-9ba7ecf.diff
Thanks for reporting this issue; yes, there is be a bug with the tresize
function which I encountered previously and which could cause this; I won't be able to have a look a this in the next two months, so in case you have the time to fix this issue, your contribution would be very welcome
should be fixed in the latest version.