| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | feat: drop `TSInstallInfo` in favor of better `checkhealth` | Christian Clason | 2025-05-12 | 1 | -4/+0 |
| | | | | | also fixes the hole in install.compilers | ||||
| * | refactor: rewrite installation using jobs and async | Lewis Russell | 2025-05-12 | 1 | -22/+6 |
| | | | | | Replace sync variants with callback support | ||||
| * | feat!: drop modules, general refactor and cleanup | Christian Clason | 2025-05-12 | 1 | -25/+77 |
| | | |||||
| * | feat!: remove obsolete `TS*` highlight groups | Christian Clason | 2022-10-16 | 1 | -10/+0 |
| | | |||||
| * | feat(highlight): re-apply default highlights on colorscheme changes | John Drouhard | 2022-07-30 | 1 | -85/+8 |
| | | | | | | | | | | | | | | | | | | | 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. | ||||
| * | refactor!: update to Neovim 0.7 APIs | Christian Clason | 2022-04-30 | 1 | -0/+121 |
| * set highlight groups via nvim_set_hl * define autocommands via nvim_create_autocmd * port plugin/nvim-treesitter.vim to Lua * port healthcheck to Lua | |||||
 |
index : nvim-treesitter | |
| [no description] | git mirrorbot |
| aboutsummaryrefslogtreecommitdiffstats |