Add shortcut to jump to next result file#42
Open
lewbei wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #34.
This adds the requested keyboard shortcut for moving from the current search result to the first result in the next file group.
Behavior:
ArrowDownstill moves to the next match as beforeCtrl+ArrowDownjumps to the first match whose file differs from the currently selected matchCmd+ArrowDownis also supported for macOS keyboardsVerification:
npm run compilepasses.I also ran
npm run lint, but the repository currently has no ESLint config file, so ESLint exits before checking source files: