I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
Looking at the repo, the author says it's to support log formats that would otherwise have to go through a "rather convoluted detour through an error file and the Quickfix window." but that's exactly how most people use it, as far as I know. That's what the quickfix window is for, so you can easily jump between errors. You don't usually paste in a line from an error log to the command arguments themselves.
Yes, but I wanted to support .vimrc:123 format because it is often used in errors of eslint, jest and other js tooling, so I can just jump to error line straight away after opening file in question without changing format.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm not sure of this vim-fetch thing.
is doing what
already does.
Looking at the repo, the author says it's to support log formats that would otherwise have to go through a "rather convoluted detour through an error file and the Quickfix window." but that's exactly how most people use it, as far as I know. That's what the quickfix window is for, so you can easily jump between errors. You don't usually paste in a line from an error log to the command arguments themselves.
Yes, but I wanted to support
.vimrc:123
format because it is often used in errors ofeslint
,jest
and other js tooling, so I can just jump to error line straight away after opening file in question without changing format.