Moving through variable segments
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- neovim, vim
- Domain
- tooling
Research direction
Start by reviewing the existing variable-segment behavior and the move-n-function and move-p-function entry points mentioned in the issue, along with the plugin documentation. Define how forward and backward variable-segment movement should work, including keybindings and dictionary configuration, then verify that the behavior and setup are documented and usable.
Written by the indexing model from the issue text.
Description
It would be nice to move forwards and back by variable segments . I just got into vim and vimscript, I looked at the code for a while and read the documentation but couldn't really figure it out. I saw that it would require setting move-n-function and move-p-function but I wasn't sure how to set up a keybinding and how to set up the dictionaries like that.
- Dominant language
- Vim Script
- Stars
- 160
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 Julian/vim-textobj-variable-segment
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Julian/vim-textobj-variable-segment#7 · 5 comments ·
All issues in Julian/vim-textobj-variable-segment
Similar issues
-
Sort modelsOpenenhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
devops documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
FlowwStar/FlowStar#991 · 2 comments ·
Maintainers usually reply within 1 day
-
bug pkg: sphinx-needs
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
useblocks/sphinx-needs#2251 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
devops dx good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
StellarLock/StellarLock#990 ·
Maintainers usually reply within 1 day