aboutsummaryrefslogtreecommitdiffstats
path: root/lua
Commit message (Collapse)AuthorAgeFilesLines
...
* Added function/method call highlight groupslfenzo2022-08-031-0/+4
|
* chore: trim space in check-healthStephan Seitz2022-08-031-1/+1
| | | | Fixes #3248
* chore: show in TSInstallInfo when parser is still loadedStephan Seitz2022-08-031-3/+5
|
* Add racket support6cdh2022-08-031-0/+11
|
* fix: node_incremental for incremental selection jumping around (#3257)itepechi / いてぺち2022-08-021-1/+6
|
* docs: add descriptions to incremental_selection keymapsStephan Seitz2022-07-311-4/+15
|
* feat(highlight): re-apply default highlights on colorscheme changesJohn Drouhard2022-07-301-0/+88
| | | | | | | | | | | | | | | | | | If the plugin is loaded after a colorscheme is set that defines any of these highlight groups, the default won't be applied. Subsequent "highlight clear" commands (common when switching colorschemes) will then clear any of those highlights, but these defaults never have another opportunity to be initialized. Effectively, if you load neovim with a colorscheme that has definitions for some of these highlight groups, then load treesitter, then switch colorschemes, many of these default links will be absent resulting in colors that do not appear the same as if that colorscheme had been used at startup. Hooking the ColorScheme event with an autocmd that just reapplies these defaults gives every colorscheme switch the opportunity to get the defaults for non-explicitly-defined groups.
* feat(ts_utils): allow starting selection after last character (#3233)Axel Dahlberg2022-07-291-2/+2
|
* fix(indents): indents for error block (css, lua) (#3207)Kiyan2022-07-211-5/+12
|
* chore: cleanup main file, move statusline in modulekiyan2022-07-182-49/+53
|
* fix(typo): utils.create_or_resue_writable_dir -> reuse (#3194)Kiyan2022-07-182-3/+3
|
* fix(indent): set only one autocmd for binding indentexpr (#3190)Kiyan2022-07-171-4/+0
|
* feat(vala)!: switch to @vala-lang parserPrinceton Ferro2022-07-091-4/+4
|
* fix: avoid installing parsers multiple times when using auto_installsmjonas2022-07-081-2/+2
|
* feat: add option to auto-install missing parsers (#3130)Jonas Strittmatter2022-07-082-0/+18
|
* Initial SQL supportderekstride2022-07-081-0/+8
|
* add qmljs (#3126)Access2022-07-071-1/+9
|
* chore: reformat with Stylua 0.14.0Christian Clason2022-07-071-6/+2
|
* docs: add description to `markdown`/`markdown_inline` in READMEStephan Seitz2022-06-281-0/+2
|
* feat(beancount): support folding org headers (#3078)PolarMutex2022-06-281-1/+1
| | | | | | requires beancount parser update Co-authored-by: Brian Ryall <brian@brianryall.xyz> Co-authored-by: Christian Clason <c.clason@uni-graz.at>
* feat(swift): compile the grammar from the main branch (#3068)Alex Pinkus2022-06-261-1/+2
| | | | The `with-generated-files` branch uses ABI 13 and therefore doesn't benefit from the ABI 14 speed improvements.
* feat(markdown)!: switch to split parser (#3048)Matthias Deiml2022-06-262-1/+39
| | | | | | | | * 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
* Chore: remove prefix from parser "location" propertyStephan Seitz2022-06-252-6/+10
| | | | | This was very confusing when using the location property as it always had to start with "tree-sitter-<lang>" for no real reason.
* Add support for custom parser install locations #2959 (#3031)Duncan McDougall2022-06-204-75/+95
|
* Add rnoweb to the parsers.lua fileBrian Albert Monroe2022-06-191-0/+9
|
* docs(swift): list alex-pinkus as maintainerChristian Clason2022-06-191-0/+1
|
* feat(tiger): initial supportBruno BELANYI2022-06-141-0/+12
|
* make ft_to_lang work for csharp (#2989)Alexej Kowalew2022-06-051-0/+1
|
* fix(health): update to upstream changesChristian Clason2022-06-021-1/+1
| | | | The `health` module was moved to `vim.health` in https://github.com/neovim/neovim/pull/18720
* fix(r): add external scannerChristian Clason2022-05-281-1/+1
|
* parser(vlang): fix location of remote repoStephan Seitz2022-05-211-1/+2
|
* feat(vlang): initial supporttami52022-05-211-0/+11
| | | | | | | | | | | | | | | | Add support for vlang filetypes. - [ ] Highlight `C` as builtin variable. This is FFI in vlang land, where C act like extern and access c functions. The vlang parser does some extension between C function calls and arguments but I believe highlighting C as builtin variable is sufficient indicator for now. I tried to use offset! but failed. Any suggestions? - [ ] Set up parser url. the vlang parser is located within [vls] repo. Is installing from nested repo supported? `tree_sitter_v/src/parser.c`? [vls]: https://github.com/vlang/vls/tree/master/tree_sitter_v cc @elianiva @theHamsta
* fix(commands): add -bar to allow other commandskiyan2022-05-141-0/+1
| | | | addresses #2920
* Add embedded template to support ERB filesNick Pezza2022-05-051-0/+8
|
* fixup: separate augroups for modulesChristian Clason2022-04-301-4/+2
|
* refactor!: update to Neovim 0.7 APIsChristian Clason2022-04-304-38/+46
| | | | | | | * set highlight groups via nvim_set_hl * define autocommands via nvim_create_autocmd * port plugin/nvim-treesitter.vim to Lua * port healthcheck to Lua
* chore!: remove ensure_installed='maintained'Christian Clason2022-04-302-23/+1
| | | | | | | | Removes all support (and tests) for the parser category "maintained", as this is no longer a useful category. BREAKING CHANGE: replace `ensure_installed='maintained'` by an explicit list of parsers, or use `'all'` (not recommended).
* feat(proto): add parserfrancisco souza2022-04-281-0/+10
| | | | Related to #2307.
* feat: add m68k parser and queriesGraham Bates2022-04-271-0/+9
|
* Add org parserTerseTears2022-04-231-0/+8
|
* fix(ts_utils): fix swap_nodes after get_node_text changefrancisco souza2022-04-212-32/+35
| | | | | | | | | | | After some discussion, it looks like the easiest thing to do for now is to keep a private copy of get_node_text (just to skip the deprecation message) and invoke that, until core provides an equivalent function that can return the node content in a table representing the node "lines". Also fixes the statusline by calling the private version for get_node_text until a change is made in core.
* adapt to vim.treesitter.query.get_node_textNir Tzachar2022-04-191-4/+4
|
* fixup: restore old implementationChristian Clason2022-04-181-1/+21
|
* fix(statusline): adjust to the new API (query)ranjithshegde2022-04-181-7/+9
|
* fix(statusline): don't use deprecated functionChristian Clason2022-04-181-3/+3
|
* chore: deprecate ts_utils.get_node_textStephan Seitz2022-04-183-31/+14
|
* chore!: remove compat module for vim.uiStephan Seitz2022-04-181-23/+0
|
* feat(swift): switch to branch with generated filesChristian Clason2022-04-181-2/+1
|
* chore: bump minimal Nvim version to 0.7 and checkChristian Clason2022-04-161-0/+4
| | | | | | Checks minimal version in `:checkhealth nvim-treesitter` Also recommend nightlies
* remove ignore_child_trees from get_node_at_positionMarcus Caisey2022-04-161-8/+15
|