Documentation of list of recognized syntax-coloring token types/styles is incomplete
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 516
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Description
(map first (racket:get-color-prefs-table)) shows 'text and 'hash-colon-keyword are missing, which if included match the ten that have entries in the “Color / Racket” preferences tab. That table is hard-coded (and the preferences tab derived from it) : https://github.com/racket/gui/blob/0fbbf759d3f244458378a639f653971fdff76668/gui-lib/framework/private/racket.rkt#L294
An 'sexp-comment token (a parsed “#;” in the racket lexer) is also styled, as a 'comment : https://github.com/racket/gui/blob/0fbbf759d3f244458378a639f653971fdff76668/gui-lib/framework/private/racket.rkt#L335-L349
A 'white-space token is styled as 'parenthesis, which presumably has no visible effect if the lexer only produces that for invisible lexemes with invisible glyphs. Not changing styles at the boundary is to reduce memory usage : https://github.com/racket/gui/commit/2da0f724923b300ab98a508018604f7d71863d62
Some 'symbol tokens get translated to 'keyword tokens based on the “Editing / Indenting” prefs, which affects their coloring : https://github.com/racket/gui/blob/0fbbf759d3f244458378a639f653971fdff76668/gui-lib/framework/private/racket.rkt#L1376-L1431
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.
Research direction
Open drracket/scribblings/tools/lang-tools.scrbl around lines 62-72, then compare its documented token types with the referenced racket:get-color-prefs-table and styling code in racket.rkt. Document the missing and specially handled token types described in the issue, and verify that the list matches the recognized and styled cases.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100