dundargoc
1727f63976
docs: fix typos
2023-03-29 18:28:56 -04:00
George Harker
cb568af539
use indent.X syntax for captures and properties of set directives
...
update CONTRIBUTING.md
adjust indents for bass
fix doc capture comment
2023-03-24 13:07:53 -04:00
George Harker
b4fcc61175
split delimiter into open_delimiter and close_delimiter
2023-03-24 13:07:53 -04:00
Amaan Qureshi
33ba346e60
feat!: add @keyword.coroutine capture
2023-03-03 07:07:52 -08:00
Preston Knopp
36b1038a65
Update gdscript queries ( #4405 )
...
* locals(gdscript): update locals
* folds(gdscript): add folds
* indents(gdscript): update indents with notes
* highlights(gdscript): update highlights
* docs(gdscript): add gdscript maintainer
* indents(gdscript): add ERROR auto indent
Co-authored-by: Amaan Qureshi <amaanq12@gmail.com>
* highlights(gdscript): use text.uri for get_node and node_path
* highlights(gdscript): add "@" of annotation as attribute
* highlights(gdscript): use keyword.operator for "new", match all attribute_call
* highlights(gdscript): update (underscore) and (pattern_open_ending)
---------
Co-authored-by: Amaan Qureshi <amaanq12@gmail.com>
2023-03-02 07:28:13 +00:00
GitHub
24f6653ffe
Update parsers: gdscript, thrift
...
update gdscript indent queries to parser change and remove @Shatur as
maintainer
2023-02-14 11:55:08 +01:00
ObserverOfTime
7c86e6ffc4
highlights(gdscript): use more specific groups
2022-11-26 13:17:51 +02:00
Ryan Roden-Corrent
f67eb83be5
feat(indent): Implement basic indent for gdscript.
...
Indent is not handled correctly when adding new lines.
It seems that functions/loops/etc. are not recognized until they have at
least one indented block.
For example, if you enter a newline after `func foo():`, the cursor will
not be indented. If you manually indent and add a line like `pass`,
e.g.:
```
func foo():
pass
```
now any insertions above or below `pass` will be indented correctly.
This might be an issue with the grammar, as it seems to apply to highlights
as well.
The following will not be highligted
```
func foo():
```
However, the following will be:
```
func foo():
pass
```
2022-01-24 13:11:01 +01:00
Lewis Russell
011ac894ec
Prefer lua-match over match
...
as string.find is much quicker than vim.regex:match*
2021-11-23 10:02:06 +01:00
Hennadii Chernyshchyk
380b49e326
Remove regex for field
2021-07-22 00:03:48 +02:00
antonk52
90f15d9bf7
feat(keywords) merge return and yield into keyword.return group
2021-07-04 21:49:17 +02:00
antonk52
bd9095e969
feat(keywords) add keyword.return & keyword.yield
2021-07-04 21:49:17 +02:00
Santos Gallegos
67f0857015
Revert "Comment: use @combined to create just one tree per buffer ( #1252 )"
...
This reverts commit 4a7a713c52
2021-05-07 16:51:57 +02:00
Santos Gallegos
4a7a713c52
Comment: use @combined to create just one tree per buffer ( #1252 )
...
* Comment: use `@combined` to create just one tree per buffer
There is no need to create a tree per line/block for comments.
Should fix https://github.com/nvim-treesitter/nvim-treesitter/issues/1251
* Add injections for scss
* Fix jsonc
* Combine jsdoc
2021-04-28 07:19:07 -05:00
Shatur95
15f27cf301
Fix identifier type check
2021-04-18 20:40:58 +02:00
Shatur95
ec9ee2757d
Fix GDScript highlighting
2021-04-18 20:40:58 +02:00
Santos Gallegos
e4083fc8e1
Add comment parser to highlight comment tags ( #893 )
...
Closes #236
2021-03-12 11:21:46 -05:00
TJ DeVries
5236768c33
add gdscript
2020-12-31 14:27:43 +01:00
