Support for :[range]g/{pattern}/[cmd]
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
Research direction
The requested entry point is the Vim command :[range]g/{pattern}/[cmd], with output remaining at the original buffer position. Start by locating existing command and search handling in the extension; done means the command supports the requested range, pattern, and command behavior without moving the current position.
Written by the indexing model from the issue text.
Description
Hi team,
Love your product - makes my time easier using VSC with a Vi based editor, particularly having access to regex.
Is your feature request related to a problem? Please describe.
I am missing the :g command. This is very useful in scanning a file for all uses of a tag (variable/function/text) without losing the context of what you are working on, ie
:g/{some tag}/p
** You are still at the same spot in the buffer **
For example if you wanted to check an expression you use in your code before adding/changing a similar line you could use :g/{part of the expression}/p to list all uses. This is very helpful when debugging code but is also useful when extending code.
Can you please prioritise this feature.
Describe the solution you'd like
Implementation of :[range]g/{pattern}/[cmd]
Describe alternatives you've considered
The only alternative to this is to search for the tag and cycle through all uses with the N/n commands before going back to the same spot in the buffer. This is clunky and time consuming.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
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.
More from VSCodeVim/Vim
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·