-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Buffer search #5597
Comments
Is Space-b not enough? |
I believe this issue is about searching the actual text in all the open buffers |
Ahh sorry my bad, I might look into actually working on it then |
#5652 allows global_search to use the content of buffer instead of reloading buffers from disk (which lead to weird mismatches before). |
Should you need to type a search term first (similar to I've been missing the latter, which I had in nvim from fzf.vim's |
you need to type the search regex first altough there are efforts to make the regex search incremental, see #4687. Fuzzy matching on lines instead of performing a regex search could also be interesting but that would probably be a second picker closer to #3462. There are some strong performance caveats with that as it essentially requires loading all files into memory (and keeping them there). I have some ideas how to avoid the issue of cloning each line if the search was constrained to open buffers (or the current) tough. That is probably the more useful application too. However for a feature like that we would want the fuzzy matching to be partially async (so it runs synchronously when fast enough but asynchronously when not, maybe we can come-up with an even smarter strategy). |
We currently have
/
for global search in workspace folder. But searching open buffers is sometimes useful. Maybe map it to[
(for open) to keep close to/
.The text was updated successfully, but these errors were encountered: