`g$` is not consistent with how vim works for lines that don't wrap
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Describe the bug
In vim g$ goes to the end of the screen when you have a long line, but it goes to the end of the line when using this extension.
To Reproduce
Steps to reproduce the behavior:
- Create a line that extends past the end of the screen without word-wrap enabled.
- Go to the beginning of the line (e.g., press
0in normal mode). - Hit
gfollowed by$.
Expected behavior
I would expect that the cursor goes to the end of the screen (with the remainder of the line staying "off screen").
Screenshots
Expected:
Actual:
Environment (please complete the following information):
- Extension (VsCodeVim) version: 1.12.4
- VSCode version: 1.41.1
- OS: Windows 10
Additional context
NA
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
The issue names no implementation file or test. Start by locating the handling for the g$ normal-mode command in the VSCodeVim extension, then reproduce the described long, unwrapped-line case and compare it with Vim; done means the cursor stops at the visible screen edge rather than the line end.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vim, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100