From f2fc44550fbe5b7ebfedc2b155dc41e93f49aedb Mon Sep 17 00:00:00 2001 From: zeertzjq Date: Thu, 26 Oct 2023 07:42:29 +0800 Subject: vim-patch:9.0.2064: cannot use buffer-number for errorformat (#25782) Problem: cannot use buffer-number for errorformat Solution: add support for parsing a buffer number using '%b' in 'errorformat' closes: vim/vim#13419 https://github.com/vim/vim/commit/b731800522af00fd348814d33a065b92e698afc3 Co-authored-by: Yegappan Lakshmanan --- runtime/doc/quickfix.txt | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'runtime/doc') diff --git a/runtime/doc/quickfix.txt b/runtime/doc/quickfix.txt index 0bf04034ec..4428ff2f65 100644 --- a/runtime/doc/quickfix.txt +++ b/runtime/doc/quickfix.txt @@ -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: > ^ -- cgit