VSCodeVim / VSCodeVim/Vim

Add `zs` and `ze` mappings to roadmap

Open
#4,487 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/feature upstream/vscode
Dominant language
TypeScript
Stars
15.2k
Forks
1.5k
Avg merge
3d 18h
Merged PRs (30d)
6

Description

Is your feature request related to a problem? Please describe.
In vim, I often use g$ without word-wrap enabled to go to the end of the screen and then use zs or ze to send the current cursor position to the beginning or end of the line, respectively.

Describe the solution you'd like
zs will scroll the window (horizontally) so that the current cursor position is moved to the far left/beginning of the screen. ze does the opposite (sends the current cursor position to the end of the screen).

Describe alternatives you've considered
I'm not aware of any alternatives.

Additional context
In vim, if my cursor is at the end of the line:
image

I can then hit zs and the screen will look like the following:
image

If the cursor is instead in the following position:
image

I can hit ze and the screen will look like the following:
image

Implementing these (or at least adding them to the roadmap) would make this extension more consistent with vim.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the TypeScript key-mapping entry point for the VS Code Vim extension and review how existing Vim window-scrolling mappings are represented. Confirm the intended horizontal behavior for zs and ze, then verify the mappings manually in an unwrapped long line; the issue does not name a file or test to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
developer-experience
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.