You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The consult package has a command consult-focus-lines that hides lines by applying a user-defined filter. The hidden lines are still in the buffer, they're just made invisible using overlays (IIUC).
If I start searching in such a filtered buffer with ctrlf and move through the matches with a repeated C-s, point jumps to the invisible matches as well, which means that you lose point, because the cursor becomes invisible.
isearch doesn't have the same issue, point only moves to the visible matches.
What would also be nice is if the match count could show not only the current match and the total number of matches, but also the number of (in)visible matches, e.g., by showing something like [5/40] (20 hidden) in the match count.
The text was updated successfully, but these errors were encountered:
joostkremers
changed the title
Don't try to jump to invisible text
Don't jump to invisible text
Jun 22, 2022
Oof, yeah. I think that's quite reasonable. There is already some support in ctrlf for handling org folding and such, but that probably has to be extended a bit.
The consult package has a command consult-focus-lines that hides lines by applying a user-defined filter. The hidden lines are still in the buffer, they're just made invisible using overlays (IIUC).
If I start searching in such a filtered buffer with
ctrlf
and move through the matches with a repeatedC-s
, point jumps to the invisible matches as well, which means that you lose point, because the cursor becomes invisible.isearch
doesn't have the same issue, point only moves to the visible matches.What would also be nice is if the match count could show not only the current match and the total number of matches, but also the number of (in)visible matches, e.g., by showing something like
[5/40] (20 hidden)
in the match count.The text was updated successfully, but these errors were encountered: