Should CamelCaseMotion ignore word separators?
Nobody has claimed this yet.
- 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.
Perhaps a continuation of https://github.com/VSCodeVim/Vim/issues/7095
Current: fiXst-word → w → firstXword
Proposed: fiXst-word → w → first-Xord
Describe the solution you'd like
Probably as simple as editing https://github.com/VSCodeVim/Vim/blob/master/src/textobject/word.ts#L193 to include word separators defined in editor.wordSeparators
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
Begin at src/textobject/word.ts around line 193 and inspect how CamelCaseMotion currently handles editor.wordSeparators. Reproduce the current and proposed motions from the issue, then verify behavior with the configured separators; done means the motion stops at the separator as shown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 62/100