| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
| |
Color can be changed by directly passing color `model` and `spec`,
so make the `name` field optional.
Signed-off-by: Jonas Dujava <jonas.dujava@gmail.com>
|
| |
|
|
|
|
|
| |
Generically, macros/commands in LaTeX starting on `if` are either
directly conditionals, or have similar purpose/funcionality.
Signed-off-by: Jonas Dujava <jonas.dujava@gmail.com>
|
| |
|
|
| |
Signed-off-by: Jonas Dujava <jonas.dujava@gmail.com>
|
| |
|
|
|
|
|
| |
Capture math delimiters provided by commands such as
`\left` and `\right`.
Signed-off-by: Jonas Dujava <jonas.dujava@gmail.com>
|
| |
|
|
|
|
|
| |
Environment names are captured as `@label` in `(begin)` and `(end)`
nodes, and so should they be when we are defining environments.
Signed-off-by: Jonas Dujava <jonas.dujava@gmail.com>
|
| |
|
|
| |
Signed-off-by: Jonas Dujava <jonas.dujava@gmail.com>
|
| |
|
|
|
|
|
| |
Apply `@nospell` to command/label names, paths, etc.
Where appropriate, turn spelling off for the whole node.
Signed-off-by: Jonas Dujava <jonas.dujava@gmail.com>
|
| | |
|
| |
|
|
| |
Signed-off-by: Jonas Dujava <jonas.dujava@gmail.com>
|
| |
|
| |
Signed-off-by: Jonas Dujava <jonas.dujava@gmail.com>
|
| |
|
|
| |
Signed-off-by: Jonas Dujava <jonas.dujava@gmail.com>
|
| |
|
|
| |
Signed-off-by: Jonas Dujava <jonas.dujava@gmail.com>
|
| | |
|
| |
|
|
| |
Signed-off-by: Jonas Dujava <jonas.dujava@gmail.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: Allowing undocumented "secret" (sub)captures makes it harder
to write comprehensive colorschemes and catch inconsistent captures.
Solution: Only allow captures listed in CONTRIBUTING.md. Add useful
(cross-language) subcaptures and drop language-specific or too niche
ones.
Follow-up: Adding further `*.builtin` captures and changing queries to
use them.
Language-specific subcaptures should instead be added in user config or
a custom language plugin.
|
| | |
|
| |
|
|
|
|
| |
Match grammar.js from commit 0d598bb95ffe3ba63403979d0d32158210974ca5 in
latex-lsp/tree-sitter-latex
Co-authored-by: gi1242 <gi1242+nvim-treesitter@gmail.com>
|
| |
|
|
|
| |
Also moves comment highlights to the very end to make them more
future-proof.
|
| |
|
|
|
| |
This commit also moves things around to give text better precedence in
the case of `textit` and `textbf`.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: Sharing highlight queries with upstream tree-sitter and
Helix is difficult.
Solution: Where reasonable, use capture names in tree-sitter's standard
list or Helix's Atom-style hierarchy.
Specifically:
* tree-sitter "standard capture names"
(https://github.com/tree-sitter/tree-sitter/blob/3f44b896852eb7daaa6df4fb778c9bb52c70c815/highlight/src/lib.rs#L20-L72):
- `@parameter` -> `@variable.parameter`
- `@field` -> `@variable.member`
- `@namespace` -> `@module`
- `@float` -> `@number.float`
- `@symbol` -> `@string.special.symbol`
- `@string.regex` -> `@string.regexp`
- `@text.*` -> `@markup.*` (`strong`, `italic`, `link`, `strikethrough`; with exceptions; see below)
- `@text.title` -> `@markup.heading`
- `@text.literal` -> `@markup.raw`
- `@text.reference` -> `@markup.link`
- `@text.uri` -> `@markup.link.url` (in markup links)
- `@string.special` -> `@markup.link.label` (non-url links)
- `@punctuation.special` -> `@markup.list` (markdown lists only; move subitems from `@text.todo`)
* Helix captures
(https://docs.helix-editor.com/master/themes.html#syntax-highlighting):
- `@method` -> `@function.method`
- `@method.call` -> `@function.method.call`
- `@text.{todo,warning,note,danger}` -> `@comment.{error,warning,hint,info,todo}`
- `@text.diff.{add,delete,}` -> `@diff.{plus,minus,delta}`
- `@text.uri` -> `@string.special.url` (outside markup)
- `@preproc` -> `@keyword.directive`
- `@define` -> `@keyword.directive`(`.define`?)
- `@storageclass` -> `@keyword.storage`
- `@conditional` -> `@keyword.conditional`
- `@debug` -> `@keyword.debug`
- `@exception` -> `@keyword.exception`
- `@include` -> `@keyword.import`
- `@repeat` -> `@keyword.repeat`
* cleanup
- remove some redundant `@conceal` (but still allow it for conceal-only patterns)
- remove obsolete `@error` (syntax linting is out of scope for this repo)
- sort, cleanup capture list in `CONTRIBUTING.md`
|
| | |
|
| | |
|
| |
|
|
| |
and italic text
|
| |
|
|
|
|
|
|
|
|
|
|
| |
As discussed in PR#5421, capturing `@error` is inconsistent, requiring
deep nesting (or priority) in order to correctly have red backgrounds to
it.
Some queries has this capture, some don't. For consistency purposes,
removing all of them is more preferable.
For re-enabling error, either add `(ERROR) @error` or `(ERROR _ @error)`
to your custom queries.
|
| | |
|
| | |
|
| |
|
| |
Add python injections to contents of `sagetex` defined environments, similarly to how `pycode` currently treated.
|
| |
|
|
|
|
|
|
|
| |
Since 0.9, @lang syntax is still available as fallback but will soon be deprecated.
Because of that, new syntax should be adopted once 0.9 becomes the
baseline requirements for nvim-treesitter
- update health check
- update doc
|
| |
|
|
|
| |
also add a few queries from Helix and remove controversial
code block conceal in Markdown
|
| |
|
|
|
|
|
| |
* Added @nospell for environment names and commands
* Added citations to @nospell
Co-authored-by: David Pikas <David.Pikas@iar.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Make use of parser updates
* add `\{re}newenvironment`
* add `\DeclarePairedDelimiter{X}`
* add `\title` and `\author`
* add optional arguments to sectioning commands
* use builtin nodes for math environments
|
| | |
|
| | |
|
| |
|
|
| |
* add \caption to @function
* only highlight contents of curly text groups in references
|
| | |
|
| | |
|