Enno
Setting `:compiler perl` inside a perl file makes more sense than using the default `gcc` compiler. Running it is a more common use case than reading grep output from a...
Would it then not be the better default, disregarding backwards compatibility for an instant, to set `&efm` to `&gfm` as the quickfix list likely is more often used for search...
Or how about an automagic educated guess by the number of matches in `&errorformat`?
Regarding the specific issue, @balki can maybe use something like ```vim command Gfile :call setqflist([], 'r', #{lines: readfile(), efm: &gfm}) ``` and a command like `:gfile` seems more convenient than...
> :gfile is the wrong abstraction That's a bit categorical; in the sense that it would lead to the addition of many commands? I wouldn't find that tragic as long...
Another question, other than as a matter of principle, is there an inherent danger in adding the ubiquitous `f:l:c:m` error format in general?
By having added a few compilers to the runtime, I naturally tend towards choosing a pertinent compiler for each file type rather than sticking to `gcc` as a matter of...
Shouldn't `:help 'switchbuf'` define this behavior?
> gawk's pretty-printer will emit only an error message when it encounters a syntax error. This can lead to the user's entire file being replaced by a two-line error message...
I thought that ```vim autocmd TerminalWinOpen * startinsert ``` could achieve this (though this would just revert to what Vim does by default), but it does not trigger for `:Floaterm`.