Fn+Up/Down (Page Up/Down) loses selection
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
What did you do?
Started a selection (Shift+v, Ctrl+v, v), pressed Fn+Up/Down to move up/down one page.
What did you expect to happen?
The selection to be extended one page up/down.
What happened instead?
The selection is lost.
Technical details:
- VSCode Version: 1.6
- VsCodeVim Version: 0.3.5
- OS: OS X 10.11.6
It works as intended if I move up or down with Fn+Shift+Up/Down, but not with the regular Fn+Up/Down.
I've had this problem with basically all Vim plugins for both VSCode, Atom and Sublime (!). That is weird indeed, and it works perfectly on Emacs or vim, which suggests I'm doing something very wrong and nobody has ever reported a movement I do 100x per day.
Can you help me understand what's going on?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in VS Code with the described Vim selection and Fn+Up/Down key sequence, then trace the keybinding and movement handling involved. The fix is complete when moving one page with Fn+Up/Down preserves and extends the active selection, while the existing Fn+Shift+Up/Down behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100