[vim/vim] Navigating quickfix and location list shouldn't create buffers to files that don't exist (#1377)
Mathias Stearn
I use the quickfix list pretty heavily, including adding an efm entry for the stack trace format in our log messages so I can use :cexpr @* to quickly navigate. I've ran into a few cases where creating buffers to non-existent files causes problems.
- The default file:line:message
efmmatches the ISO8601-formatted timestamps on every line. This creates buffers with Y-M-DTH file names whenever I:cnextover a line that doesn't match other formats. - Some tools use ??:?? when they can't figure out the file and line info (eg no debug symbols for the library) and I don't want a file named ??.
- Windows paths use \ which isn't converted to / on linux.
I think the ideal solution would be to make the efm parser not match %f for files that don't exist (or add a new specifier for this purpose). It could then continue looking for other formats that match. Alternatively, having :cnext skip over entries for files that don't exist would solve this pain point.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
David M. Lary
came across this issue when running a make test that output ISO8601 timestamps. The workaround is to update errorformat to skip these messages:
" prepend a rule to ignore, but not suppress, lines that start with ISO8601 timestamps set efm^=%+G%\\d%\\{4}-%\\d%\\d-%\\d%\\dT%\\d%\\d:%\\d%\\d:%\\d%\\d%.%#
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
David Pape
zyzzyxdonta left a comment (vim/vim#1377)Old issue, but for the record, many other formats are also affected.
With a Makefile like this:
default: @echo 'x: x:0:x'
Running :make, the quickfix list shows (1 of 1): x, and a new empty buffer called x: x is created.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Enno
Konfekt left a comment (vim/vim#1377)As another example, make --print-directory lists files with path make for the entered directories.
make the efm parser not match %f for files that don't exist (or add a new specifier for this purpose)
This sounds sensible and shouldn't be difficult to implement and hardly something that others historically rely on, or are there any principal blockers (question to the maintainers) ?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Yegappan Lakshmanan
yegappan left a comment (vim/vim#1377)As another example,
make --print-directorylists files with pathmakefor the entered directories.make the efm parser not match %f for files that don't exist (or add a new specifier for this purpose)
This sounds sensible and shouldn't be difficult to implement and hardly something that others historically rely on, or are there any principal blockers (question to the maintainers) ?
The '%D' and '%X' format specifiers are used to handle entering and leaving directories during the
make process. The proper errorformat setting should be used to parse the output.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Enno
Konfekt left a comment (vim/vim#1377)The '%D' and '%X' format specifiers are used to handle entering and leaving directories during the
make process. The proper errorformat setting should be used to parse the output.
Yes, so should compiler/gcc.vim and bd5e882 be adapted accordingly?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Enno
Konfekt left a comment (vim/vim#1377)Mind that this is an aside, I didn't intend to take over this issue's original cause
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.