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
When doing a bidirectional search, the next_target and prev_target keybindings doesn't work. I would love if next_target would jump to the next match in the direction of the end of the buffer and prev_target would jump in the other direction.
The text was updated successfully, but these errors were encountered:
You can use repeat keys (:h leap-repeat), which effectively do the same.
To make traversal mode work for non-directional motions, we should maintain additional tables (winlocal-directional-idx : original-idx) for each window, I'm not sure it would worth the effort. But I will give it some thought.
ggandor
changed the title
bidirectional search - next_target and prev_target not working
Allow traversing the matches directionally after bidirectional search
Mar 30, 2024
ggandor
changed the title
Allow traversing the matches directionally after bidirectional search
Allow traversing directionally after bidirectional search
Mar 30, 2024
When doing a bidirectional search, the next_target and prev_target keybindings doesn't work. I would love if next_target would jump to the next match in the direction of the end of the buffer and prev_target would jump in the other direction.
The text was updated successfully, but these errors were encountered: