| Age | Commit message (Collapse) | Author |
|---|
|
Some languages that are difficult to parse via Treesitter may
incorrectly include whitespace lines at the end of regions. This can
makes the calculated folds sub-optimal.
To recitfy, use a custom directive (trim), to calculate the range with
the trailing whitespace lines removed. Note this only works if the
region end column is 0.
Also added folds for Make.
|
|
* switch to split markdown parser with separate block and inline parsers to improve performance
* add exclude_children! directive (useful for something like Injected markdown incorrectly highlights indented docstrings #2212)
* split markdown queries into block and inline ones and add the injection for inline into block grammar
* add include_dir option to parser configs (needed because the two grammars don't live in the repos root directory)
BREAKING CHANGE: downstream queries need to be adapted to new parser
|
|
|
|
|
|
get_node_text could be nil if the range is invalid.
With https://github.com/neovim/neovim/pull/15030/
this fixes https://github.com/nvim-treesitter/nvim-treesitter/issues/1531
|
|
|
|
```
(#downcase! "language")
```
downcase! will ensure the metadata value for the specified key will be
downcased. If the value is a node, it will downcase the text specified
by the node.
```
(#downcase! @node "key")
```
You can also namespace the key with a specific capture, similar to how
you can call `(#set! @node "key" "value")`
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
