-
Notifications
You must be signed in to change notification settings - Fork 37
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
bug: better handling of folds #39
Comments
Could this be an option? Jumping to folds is quite useful sometimes |
Whats the use-case? Using incremental mode? |
No, just navigation. Sometimes I wanna jump to a fold and open it because the code I must read/modify is folded |
It doesn't seem to be possible to set extmarks on the folded line. With something like nvim-ufo, you will see the markers |
@folke what do you mean? I'm using |
@MariaSolOs I mean you can jump to the summary shown on the fold for a word in that fold. Still need to make it so that a folded line also gets a label (one) when the text inside the fold matches the pattern. |
Why limit the label to the first match? Not asking you to change this BTW, I'm just curious :) |
Since you can't see the targets you are jumping to, I don't think it makes sense to show all the labels for items in the folds? |
@folke What I had in mind is that say I'm jumping to the following line with
I thought something like this would happen (adding the labels to both occurrences of
|
Oh you mean on the foldtext? That's not how it currently works. It's also not straightforward to map actual cursor positions to a position inside the foldtext. The feature I did add is say you have a multiline fold and the pattern matches something in line 3 of your fold, then you'd still be able to jump to that |
That makes sense, thanks for explaining! |
Did you check the docs?
Is your feature request related to a problem? Please describe.
currently matches inside folds are labeled
Describe the solution you'd like
need to think this through :)
Describe alternatives you've considered
not really
Additional context
No response
The text was updated successfully, but these errors were encountered: