Using neovim, some space at the beginning of a line is treated differently than other characters
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
- Click thumbs-up 👍 on this issue if you want it!
- Click confused 😕 on this issue if not having it makes VSCodeVim unusable.
The VSCodeVim team prioritizes issues based on reaction count.
Environment:
- VSCode Version: 1.13.1
- VsCodeVim Version: 0.8.6
- OS: Win10
-Other extensions: [C# 1.10.0]
What happened:
I was doing a poor-man's 2-space indent:
:%normal i<space bar><space bar>
Then, I wanted to outdent a line, so I did:
:%normal xx
It deleted two spaces in the first stroke and either 1 non-space character, or the next two-space pair.
What did you expect to happen: I expected the indented text to have the initial two space characters removed.
How to reproduce it:
:normal >>0xx
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
Reproduce the behavior with :normal >>0xx after adding two leading spaces using :%normal i<space bar><space bar>. Trace the TypeScript handling of normal, cursor movement, and leading whitespace, then verify that xx removes exactly the two initial spaces without deleting adjacent text.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- neovim, typescript, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100