[vim/vim] Proposal: Add support for colon delimited line number when opening files (Issue #9144)
daniel baak
Many compilers, runtimes and loggers output lines containing filename colon line number.
Currently i need to run vim /home/user/repo/myfile +123 to open a file at line number 123.
I'd like to instead run vim /home/user/repo/myfile:123; i.e. just cut and paste the log output including the line number into my command line.
I'd expect this behaviour to also apply to :tab new :vsp etc. (as the +123 version does now).
The +123 version would still have to be supported, in order not to break existing workflows and or scripts.
I know it's a minor difference, but it's a common usecase for me and I'm curious if others feel the same.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub.
Triage notifications on the go with GitHub Mobile for iOS or Android.
lacygoill
You might be interested in one of these plugins:
daniel baak
Closed #9144.
carli2
carli2 left a comment (vim/vim#9144)You might be interested in one of these plugins:
* [vim-fetch](https://github.com/wsdjeg/vim-fetch) * [file-line](https://github.com/lervag/file-line) * [search-and-view](https://github.com/lilydjwg/search-and-view)
I tried https://github.com/lervag/file-line and it didn't work. vim info:5 opens a new file called info:5 instead of opening file info at line 5
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Christian Brabandt
chrisbra left a comment (vim/vim#9144)ping @lervag then
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Karl Yngve Lervåg
lervag left a comment (vim/vim#9144)My file-line plugin works as expected for me. Feel free to open an issue on the repo @carli2.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.