From ca88ad10c8e9eeee2f2bf1bc73466d207663c4d2 Mon Sep 17 00:00:00 2001 From: zeertzjq Date: Fri, 14 Aug 2026 07:46:52 +0800 Subject: [PATCH] vim-patch:e402d1c: runtime(doc): improve documentation for |v_gF| (#41300) https://github.com/vim/vim/commit/e402d1c443ec9f542df0503d765a09c32eabd7b4 Co-authored-by: Emilien Breton --- runtime/doc/editing.txt | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/runtime/doc/editing.txt b/runtime/doc/editing.txt index cd87ee1d22..128913a7f0 100644 --- a/runtime/doc/editing.txt +++ b/runtime/doc/editing.txt @@ -304,15 +304,20 @@ CTRL-^ Edit the alternate file. Mostly the alternate file is character. " line " is also recognized, like it is used in the output of `:verbose command UserCmd` White space between the filename, the separator and - the number are ignored. + the number is ignored. Examples: eval.c:10 ~ eval.c @ 20 ~ eval.c (30) ~ eval.c 40 ~ + eval.c line 50 ~ *v_gF* -{Visual}[count]gF Same as "v_gf". +{Visual}[count]gF Same as "v_gf", but if a colon and a number appear + immediately after the end of the selected text, + then the cursor is positioned on that line in the + file. Unlike |gF|, only a colon is recognized as + separator. These commands are used to start editing a single file. This means that the file is read into the buffer and the current file name is set. The file that