Should CamelCaseMotion ignore word separators?

Open Beginner friendly
#8,485 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
typescript, vscode

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.

Description

Is your feature request related to a problem? Please describe.
Perhaps a continuation of https://github.com/VSCodeVim/Vim/issues/7095

Current: fiXst-wordwfirstXword

Proposed: fiXst-wordwfirst-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

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

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.

More from VSCodeVim/Vim

All issues in VSCodeVim/Vim

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.