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
{{ message }}
This repository has been archived by the owner on Oct 21, 2022. It is now read-only.
; actual:
matches are still highlighted, but cursor is not advance
;expected
cursor advanced to next match
More explicit steps to reproduce:
Open an editor tab for a while with some text.
In normal mode type / to open the find bar at the bottom of the tab.
In the find find textbox, type something for which there are at least several results in the editor text, e.g. a, and then hit Enter.
Navigate so that cursor is not at the beginning of the first (or next) search result, e.g. hit l several times.
Type / to bring up the find bar again and then hit Enter.
In Vim, the cursor should advance to the next search result. In the latest version of Light Table [technically, a current source build of LT], the previous search result is highlighted but the cursor does not move. Using n or N (in normal mode) still works as expected.
The text was updated successfully, but these errors were encountered:
kenny-evitt
changed the title
In normal mode, <kbd>/</kbd> <kbd>Enter</kbd> doesn't advance to the next search result
In normal mode, <kbd>/</kbd> <kbd>Enter</kbd> doesn't advance to the next search result (for the previous search)
Dec 6, 2015
I couldn't reproduce this just now with the latest CodeMirror Vim bindings demo, which is what our Vim plugin uses. But it's unclear whether the cause of this bug is the CodeMirror Vim code or the LT plugin code.
This covers LightTable/LightTable#566. The original comment:
More explicit steps to reproduce:
In Vim, the cursor should advance to the next search result. In the latest version of Light Table [technically, a current source build of LT], the previous search result is highlighted but the cursor does not move. Using n or N (in normal mode) still works as expected.
The text was updated successfully, but these errors were encountered: