Vim-fork focused on extensibility and usability http://git.waynecole.info/neovim/atom?h=master 2025-02-22T12:07:21Z 2025-02-22T12:07:21Z Christian Clason c.clason@uni-graz.at 2025-02-22T12:07:21Z urn:sha1:2e5b560482fb76342387e7183283efe9d431f114 Problem: It's difficult to navigate large structured text files (vim help, checkhealth, Markdown). Solution: Support `gO` for table of contents and `]]`/`[[` for moving between headings for all these filetypes using treesitter queries. Refactor: colorization of highlight groups is moved to the `help` ftplugin while headings-related functionality is implemented in a private `vim.treesitter` module for possible future use for other filetypes. 2025-01-15T03:55:29Z Maria José Solano majosolano99@gmail.com 2025-01-14T03:39:03Z urn:sha1:850084b519e18122820478a71bb4bfa4c15e528a 2024-09-27T22:31:45Z Riley Bruins ribru17@hotmail.com 2024-09-14T19:57:33Z urn:sha1:0f067cd34d09b38f9aaf2e1732d825e89b573077 2024-09-13T12:09:11Z Riley Bruins ribru17@hotmail.com 2024-09-13T12:09:11Z urn:sha1:b9b408a56c7e607972beaa7214719ff1494e384c **Problem:** `vim.treesitter.get_parser` will throw an error if no parser can be found. - This means the caller is responsible for wrapping it in a `pcall`, which is easy to forget - It also makes it slightly harder to potentially memoize `get_parser` in the future - It's a bit unintuitive since many other `get_*` style functions conventionally return `nil` if no object is found (e.g. `get_node`, `get_lang`, `query.get`, etc.) **Solution:** Return `nil` if no parser can be found or created - This requires a function signature change, and some new assertions in places where the parser will always (or should always) be found. - This commit starts by making this change internally, since it is breaking. Eventually it will be rolled out to the public API. 2024-06-09T11:54:34Z Christian Clason c.clason@uni-graz.at 2024-06-08T08:49:15Z urn:sha1:6592873f773b4c358ea950bfcfa8cbc3fc3bc8cc Problem: Creating the table of contents for `gO` is complicated. Solution: Use treesitter instead. 2023-12-20T17:58:40Z Christian Clason c.clason@uni-graz.at 2023-12-18T15:49:44Z urn:sha1:cc6a257c8cad8051b6f7e9287249293ab0a929d9 Problem: Not all default highlight groups show their actual colors. Solution: Refactor `vimhelp.lua` and apply it to all relevant lists (UI groups, syntax groups, treesitter groups, LSP groups, diagnostic groups). 2023-09-08T13:05:35Z zeertzjq zeertzjq@outlook.com 2023-09-08T13:05:35Z urn:sha1:d0d4160dd13fad952338b8582e2db8838172bbf1 - Add runtime/lua/vim/vimhelp.lua, which is a translation of Vim's runtime/import/dist/vimhelp.vim. - Unlike Vim, run the highlighting from an ftplugin file instead of a syntax file, so that it is run even if using treesitter.