Feature Vision Discussion: Syntax Highlighting
Open
Nobody has claimed this yet.
A-SyntaxHighlight
- Dominant language
- Rust
- Stars
- 818
- Forks
- 249
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 30
Description
This issue is part of the larger vision discussion managed in #63 to brainstorm and prioritize ideas around features that would make reedline as a line editor for you both viable as well as pleasant to use. Feel free to up-vote features you depend on in other tools/shells as well as suggest new ideas!
Syntax Highlighting Features
- Ability to define word-types to highlight as you type and continue coloring even in failure modes
- Keywords
- Commands
- External Commands
- Bareword
- Punctuation
- Sub-Commands
- Braces
{}, Brackets[], Parentheses() - Error modes
- Operators
- Paths
- Pipe
- Arguments/Flags
- Variables
- Comments
- DataTypes (strings, int, datetime, duration, bool, units, etc)
- Other
- Ability to have add things you want syntax highlighted through extensibility
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
Start with the larger vision discussion in issue #63 and review the syntax-highlighting checklist here. Define a focused scope for one unchecked highlighting capability, including how extensibility should work and what completion criteria would be. No source files or tests are identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100