mirrors/neovim
1
0
Fork 0
mirror of https://github.com/neovim/neovim.git synced 2026-03-24 17:40:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

vim-patch:9.0.2064: cannot use buffer-number for errorformat (#25782)

Browse Source 
Problem:  cannot use buffer-number for errorformat
Solution: add support for parsing a buffer number using '%b' in
          'errorformat'

closes: vim/vim#13419

b731800522

Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
This commit is contained in:
zeertzjq
2023-10-26 07:42:29 +08:00
committed by GitHub
parent bfe8a39512
commit f2fc44550f
3 changed files with 90 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
runtime/doc/quickfix.txt
View File

@@ -1381,6 +1381,7 @@ rest is ignored. Items can only be 1023 bytes long.
Basic items
%f file name (finds a string)
%b buffer number (finds a number)
%o module name (finds a string)
%l line number (finds a number)
%e end line number (finds a number)
@@ -1420,6 +1421,11 @@ On Windows a leading "C:" will be included in "%f", even when using "%f:".
This means that a file name which is a single alphabetical letter will not be
detected.
The "%b" conversion is used to parse a buffer number. This is useful for
referring to lines in a scratch buffer or a buffer with no name. If a buffer
with the matching number doesn't exist, then that line is used as a non-error
line.
The "%p" conversion is normally followed by a "^". It's used for compilers
that output a line like: >
^