Skip to content
This repository has been archived by the owner on Oct 21, 2022. It is now read-only.

In normal mode, <kbd>/</kbd> <kbd>Enter</kbd> doesn't advance to the next search result (for the previous search) #63

Open
kenny-evitt opened this issue Dec 6, 2015 · 1 comment

Comments

@kenny-evitt
Copy link

This covers LightTable/LightTable#566. The original comment:

;in vim-mode
/word

; highlights matches

/

; actual:
matches are still highlighted, but cursor is not advance

;expected
cursor advanced to next match

More explicit steps to reproduce:

  1. Open an editor tab for a while with some text.
  2. In normal mode type / to open the find bar at the bottom of the tab.
  3. 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.
  4. Navigate so that cursor is not at the beginning of the first (or next) search result, e.g. hit l several times.
  5. 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.

@kenny-evitt 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
@kenny-evitt
Copy link
Author

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant