[vim/vim] runtime(doc): document |v_gF| (PR #21034)

[Emilien Breton]

The relevant line-obtaining logic is in grab_file_name().

---

You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/21034

Commit Summary

• 9c4556a runtime(doc): document |v_gF|

File Changes

(1 file)

• M runtime/doc/editing.txt (6)

Patch Links:

• https://github.com/vim/vim/pull/21034.patch
• https://github.com/vim/vim/pull/21034.diff

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/21034@github.com>

[Christian Brabandt]

chrisbra left a comment (vim/vim#21034)

that is not correct. Try editing a new buffer from Vims repo with this content:

:set hidden
src/eval.c:499

place the cursor on it, press gF, Vim jumps to src/eval.c line 499, visual selection the line and pressing gF errors out with

E447: Can't find file "src/eval.c:499" in path

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/21034/c5272313900@github.com>

[Emilien Breton]

Bricktech2000 left a comment (vim/vim#21034)

With a linewise selection I get the same error as you do.

The visual selection should look like [src/eval.c]:499, i.e., contain the file name and path but not the colon or the line number. Let me know if that works. Maybe I should rephrase the documentation to clarify this?

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/21034/c5272897122@github.com>

[Christian Brabandt]

chrisbra left a comment (vim/vim#21034)

yeah, then we should clarify this behaviour. Thanks

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/21034/c5276935550@github.com>