Please provide symbol lookup for the identifiers used amongst `syn match`, `syn region`, and `syn cluster`.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- vim
- Domain
- tooling
Research direction
Start by examining the syntax files under .vim/syntax, using syntax/bind-named.vim and syntax/nftables.vim as large examples. Trace how syn match, syn region, and syn cluster identifiers are parsed, then determine how symbol lookup should expose definitions and references such as contains, nextgroup, and containedby. Done means these identifiers can be found through the parser's symbol lookup support.
Written by the indexing model from the issue text.
Description
Often times, the syntax spec file (ones in the .vim/syntax directory, have hundreds, if not thousands of identifiers.
And having the support of the symbol table would greatly cut down lookup efforts (instead of currently doing the selection-word, cut-n-paste into a search bar).
The symbol definition of such identifiers are defined in:
syntax match this_symbol_name ...
syntax region this_symbol_name ...
syntax cluster this_cluster_symbol_name ...
And are easily referenced after keywords like:
\ contains=this_symbol_name[,next_symbol_name ...]
\ contains=@this_cluster_symbol_name[,next_symbol_name ...]
\ nextgroup=this_symbol_name[,next_symbol_name ...]
\ containedby=this_symbol_name[,next_symbol_name ...]
Support for this will greatly assist the large data science community with easier and even simplistic syntax highlight used against high-speed data streaming outputs.
For large working examples:
- Dominant language
- Vim Script
- Stars
- 173
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 vim-jp/vim-vimlparser
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
vim-jp/vim-vimlparser#200 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
vim-jp/vim-vimlparser#198 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
vim-jp/vim-vimlparser#197 · 2 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
vim-jp/vim-vimlparser#191 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
vim-jp/vim-vimlparser#174 ·
All issues in vim-jp/vim-vimlparser
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
use-agent-os/agent-os#3314 ·
-
documentation low-priority templates
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
jesseray718/openroot#87 ·
-
factory-active factory-automatic task-bug-reproduction-cannot-reproduce task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
in-progress proposal
Difficulty 1/5 Under an hour Newbie friendliness 88/100
uibcdf/molsyssuite#36 ·