You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<c-w>f doesn't take me to the line number within the file, whereas gF does, but only within the same window.
My use case is, from bash, going:
somegrep somestring | vim -
which gives me a list of files. If i were to gF on a result, I get the yes/no/cancel dialog to confirm I want to lose that page forever. I don't - hence my use of <c-w>f to open the result in another window. Ideally vim-fetch would do this AND jump to the correct line within that file.
The text was updated successfully, but these errors were encountered:
Duh, I wasn’t even aware of the CTRL-W file lookup commands until now. This looks tricky as the commands perform a lookup of the file before splitting, so vim-fetch will have to override the whole operation. I’ll file your suggestion under future enhancements, but I must warn you I cannot provide an ETA, as I have no inkling of when I will have time to invest into this plugin again.
<c-w>f
doesn't take me to the line number within the file, whereasgF
does, but only within the same window.My use case is, from bash, going:
somegrep somestring | vim -
which gives me a list of files. If i were to
gF
on a result, I get theyes/no/cancel
dialog to confirm I want to lose that page forever. I don't - hence my use of<c-w>f
to open the result in another window. Ideally vim-fetch would do this AND jump to the correct line within that file.The text was updated successfully, but these errors were encountered: