Christian Brabandt

I thought about that. But we would also have to specify a separator between each part. Like the colon mentioned before... Am 2021-02-19 19:48, schrieb Subhaditya Nath: > @PlasmaHH [1]...

I am pretty sure it does not matter in practice.

can you check if this is a recent regression? (e.g. git bisect the offending commit?)

On Mi, 08 Jul 2020, Andrea Cardaci wrote: > Apparently bc8fdfe946e1a3dd8b711d5bab1a3de13a5449d9 is the first bad commit. That is the one I would have guessed :/ Best, Christian -- Frauen sind...

This seems to happen, because netrw does reset the `buflist`option for that buffer. I wonder if it makes sense to remove the `buflist()` check in `airline#extensions#tabline#buflist#list()` Please try this patch:...

hm. What terminal is this? Is this about the buffer names in the statusline or in the tabline (or both)? Does it happen without tmux/screen? What about in a different...

That is wrong. If I have created a location list by e.g. using lvimgrep then syntastic shouldn't close it, just because there is no error when compiling that file. It...

Here is a patch, that works for me. Please consider merging https://github.com/chrisbra/syntastic/commit/b8eb1d27dd92449ebf7278567fc64f4c02883387

Indeed. I still find it disappointing, that this breaks several plugins, that create a location list for themselves. There must be a simpler way for syntastic to not mess with...

I don't mind, having to create a new location list if syntax errors are found, but if not, it should still leave the old location list alone