Discovered today that the following doesn't do what I hoped (though I
can understand why). To demonstrate
$ mkdir a b
$ cd a
$ echo hello > included.txt
$ echo include included.txt > including.txt
$ cd ../b
$ ln -s ../a/including.txt include_in_b.txt
$ vim include_in_b.txt
Now putting the cursor on "included.txt" in the file and using either
is unable to find the target/included file because the linked file is
actually in a remote folder. Of course, doing
$ cd ../a
$ vim including.txt
or
:cd ../a
inside vim works as expected, letting me use "gf" and friends to jump
to the included files without issue.
Is there a simple way to get "gf"/"^Wf" (and any others in the same
family of functions) to chase the link to find the corresponding file
as if that target's directory was in 'path'?
Thanks!
-tim
(the actual context is a remind(1) reminder file where ~/.reminders
is a link to ~/.config/remind/reminders.rem which includes each of my
individual calendar files are in that ~/.config/remind/ directory, so
editing ~/.reminders doesn't give me quick access to the per-calendar
subfiles that get included if I use "gf" and friends)
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Monday, November 5, 2018
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment