How do you handle this workflow in Helix? (Quickfix list)

[leo-unglaub]

Hey,
i would love to hear your thoughts on how you solve this very common problem/practice. When i am working in a project it happens very often, that i have to change something in multiple places. Here is an example:

I have changed how a function works, i did not just rename it, i changed how i have to call it. So i cannot use the LSP rename for everything. I have to look up all instances where i call this function and then fix them one after another.

Before Helix i was a Vim user and in there i searched for all instances that needed work, put them in the Quickfix list and worked on them until i was done. That way i had a list of all places that i need to fix and i could not forgett about them.

But since i moved to Helix i cannot do that anymore. I tried the following workarounds, but i always end up with a problem.

1. I use the global search <space>/ and filter the list down to what i need. For example foobar( !resources !tmp .rs. Then i go to the first file and fix the issue. Then i pull up the latest picker again using <space>'. This works kind of fine until you have to use the a picker for something else. Then all your, sometimes complex, search queries are gone. Another small problem with this is, that if i reopen the latest global search it does not update automatically. So i have to change something to trigger a new search.
2. I use the global search, do a screenshot of the list of places if have to work on and then .... well, you can already see why this sucks :D

I search old discussions here on Github and in the chat and as far as i understand it the devs really hate the idea of a quickfix list in the style of Vim. While i totally respect there desicion, i wonder how you solve this very common coding task. I fully understand that you dont want to Convert a small and lightweight Editor into a bloated IDE, but this seams like a common usecase for a text editor.

If you don't want a Vim-Style Quickfix list, there are some possible solutions that would also work and would be simple to do.

1. Ability to store a global search in a register. If we could store the state of a global search in a register, we could simply create a workflow where we use a custom register to store the current quickfix list. Example "t<space>/. That way i know i can pull up my current todo from "t. Another benefit from this would be, that we could have as much quickfix lists as we have registers. So i could have on for fixing problem X and one for fixing problem Y.
2. Ability to copy the current picker into an empty buffer. If we could get all paths from the current picker into an empty buffer, we could just use goto_file on each line on that empty buffer and even remove lines if we are done fixing them.

I am interrested in hearing your thoughts on this.
Thanks and greetings
Leo

[Dotrar]

Another kinda dirty option is to add a keybind in your config. I have these two for "find word under cursor":

"#" = "@miw/<C-r>.<ret>"
"@" = "@miw<space>/<C-r>."

Can you link the discussions you found about quickfix? I never really was able to get the flow of qf, but if there was a way to have a harpoon like functionality.. (edit, we do, it's called the jumplist)

I have found we have a "jumplist" but with not much work done to it. (PR: #3720) - you can add points as a jumplist, but it would be nice to select picker choices -> send to jumplist