New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide API to just resolve specs #13
Comments
That is a) definitely possible and b) a major refactoring of the codebase. Before undertaking it, I would like to understand your exact use case. Is it just a matter of using fetch to parse a spec’ed |
What I want is to basically use the improved My hack for this is the following in
|
yeah, a nice feature request. Maybe be this plugin could provide a function and accept a dict argv:
with this function, user can create there own mappings. for example,
|
I've thought to use this plugin to get the filename under the cursor in a quickfix list, and then
:edit
it afterwincmd w
.From a quick glance
fetch#cfile
does this, but the command to be executed is hard-coded togf
/gF
already.It would be great to have an interface where the filename that would be understood by vim-fetch would be returned: empty would mean that vim-fetch (and
gf
/gF
) cannot handle it.For my use case using the current cursor position is good, but I could also imagine passing in a string (and maybe the position in that string).
Another approach would be for the function to return the spec itself: the filename and the jump action (and a way to call / execute those).
The text was updated successfully, but these errors were encountered: