-
Notifications
You must be signed in to change notification settings - Fork 86
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
Populate CtrlSF from traditional quickfix list? #252
Comments
Maybe something like |
It's almost impossible because the context lines to show must exist at first, but in your case, they do not exist at all in anywhere of Vim. But what plugin are you using to populate the quickfix? If it does also read result from a grep-like program, maybe CtrlSF could adopt that as a new backend. |
Not a new grep-like, it's just ag under the hood. I'm using two plugins actually, fzf.vim and vim-agriculture. Fzf.vim has this awesome realtime filtering post-search that's a big part of my workflow. And agriculture provides an awesome That said, I absolutely love CtrlSF post-search, with how you display and allow editing of results 🔥 But I'd like to combine that with my own call to
If we can't populate from the quickfix, I actually have access to the both the raw ag output, and the filtered results from fzf.vim. Maybe I can pass my ag output into CtrlSF via a function call somehow? PS. Not sure if you are open to chatting more on Discord? If so, hit me up at jesseleite#8296! |
Ok, I have got your point, it seems quite possible now. Suppose you have read the source code, add a new argument (like Make sure it does not interfere with the async mode. |
Like?
Or a new command like?
|
Looks like the |
Can CtrlSF results be populated from a traditional quickfix window? I'm using another plugin which populates the quickfix, and it'd be cool if we could call a function to transfer what's in the quickfix to CtrlSF to see more context and use CtrlSF's edit mode on the results of this other plugin 😬
The text was updated successfully, but these errors were encountered: