summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorStephan Seitz <stephan.seitz@fau.de>2021-12-01 20:33:18 +0100
committerKiyan <yazdani.kiyan@protonmail.com>2021-12-06 20:57:50 +0100
commit913b72d60d3ccf6fd9af1edd80aba7c713e35d01 (patch)
tree164eeb9b389fb54b2f202f9160238068fe1fabf5 /README.md
parentd6a0a26b8563409d4660def7320a4f4bc23954df (diff)
docs: remove advice to use 0.5-compat
0.5-compat branch was not actively maintained and nvim-treesitter also runs with stable versions. We should be able to maintain compatibility with latest stable by fall-back implementations in case there should be a breaking change.
Diffstat (limited to 'README.md')
-rw-r--r--README.md7
1 files changed, 2 insertions, 5 deletions
diff --git a/README.md b/README.md
index c3349201..f2bf2339 100644
--- a/README.md
+++ b/README.md
@@ -37,14 +37,11 @@ Traditional highlighting (left) vs Treesitter-based highlighting (right).
More examples can be found in [our gallery](https://github.com/nvim-treesitter/nvim-treesitter/wiki/Gallery).
**Warning: Treesitter and nvim-treesitter highlighting are an experimental feature of nightly versions of Neovim.
-Please consider the experience with this plug-in as experimental until Neovim 0.6 is released!
+Please consider the experience with this plug-in as experimental until Tree-Sitter support in Neovim is stable!
+We recommend using the nightly builds of Neovim or the latest stable version.
You can find the current roadmap [here](https://github.com/nvim-treesitter/nvim-treesitter/projects/1).
The roadmap and all features of this plugin are open to change, and any suggestion will be highly appreciated!**
-*If you want to use this plugin with Neovim 0.5, please use the
-0.5-compat branch. Be aware though that most improvements will require
-neovim nightly.*
-
Nvim-treesitter is based on three interlocking features: [**language parsers**](#language-parsers), [**queries**](#adding-queries), and [**modules**](#available-modules), where *modules* provide features – e.g., highlighting – based on *queries* for syntax objects extracted from a given buffer by *language parsers*.
Users will generally only need to interact with parsers and modules as explained in the next section.
For more detailed information on setting these up, see ["Advanced setup"](#advanced-setup).