tree-sitter VS nvim-tree.lua

I learned from a google search that these days upstream tree-sitter provides WebAssembly bindings.

Source: https://github.com/tree-sitter/tree-sitter/tree/master/lib/b...

NPM: https://www.npmjs.com/package/web-tree-sitter

Download from the latest Github release: js file (https://github.com/tree-sitter/tree-sitter/releases/download...) and wasm file (https://github.com/tree-sitter/tree-sitter/releases/download...)

Tree-sitter optimizes for performance (to use in editors), not for correctness. In fact even TS' core developers advocate for not bothering too much with correctness of grammars[1]. I imagine this constraint would be a deal-breaker for GitHub or anyone else in their position.

[1] https://github.com/tree-sitter/tree-sitter/issues/130#issuec...

This is a plugin that provides a simple way to use the tree-sitter in Neovim and also provides functionalities like highlighting, etc.

From the tree-sitter side, I am tracking https://github.com/tree-sitter/tree-sitter/issues/1942

Is tree-sitter really slower than TextMate grammars? Some benchmarks indicate that this isn't really the case [1]. On the other hand, breaking parse trees is a real issue, because the error-recovery in tree-sitter is pretty rudimentary [2][3], but as you said, it's not an issue for Shiki.

Several TextMate grammars suffer from inaccuracy bugs, and issues of maintainability. Perhaps the biggest hindrance in the adoption of tree-sitter, is that the most popular editor, VSCode, still doesn't support it.

[1]: https://github.com/microsoft/vscode/pull/161479

[2]: https://github.com/tree-sitter/tree-sitter/issues/1870

[3]: https://github.com/tree-sitter/tree-sitter/issues/224

u/lewis6991 I think the biggest performance gain was made by tree-sitter itself: https://github.com/tree-sitter/tree-sitter/pull/2085

I asked on the repo's discussions but responses are limited and not explanatory (I'm not shaming anyone here, discussions aren't a place for detailed how-tos and documentations anyway).

The following discussion here. TS query cannot be incremental, that is why I regard it as design fault.

Hi, so I've recently decided to give Neovim yet another try, this time using some predefined plugins with kickstart.nvim, for syntax it uses tree-sitter.

This works for installing the other plugins. But I can't seem to access nvim-tree. According to the website (https://github.com/nvim-tree/nvim-tree.lua), I should be able enter :NvimTreeOpen in neovim, but I get "Not an editor command: NvimTreeOpen." Any ideas?

For splitting the terminal you could try either toggleterm or tmux. If you want to send things from one tmux pane to another, then you can use slime. For a toggle-able filetree, you can use nvim tree.

(Neovim) nvim-tree

Also you can use your file browser such as neo-tree, nvim-tree, or even netrw.

I have almost finished customize nvim tree to equal bg colors. Can't resolve only when nvtree out of focus. What of paramets i should write? I tryied from this https://github.com/nvim-tree/nvim-tree.lua/blob/master/doc/nvim-tree-lua.txt but nothing

I was having an issue with my colorscheme Sonokai and I found my issue

Personally I use will133/vim-dirdiff plugin, but it is pretty troublesome as I need to invoke `:DirDiff /path/to/dir1 /path/to/some/dir2`. What would be ideal is to extend nvim-tree, to be able to mark two directories (in similar manner as it has bookmarks) and then execute `:DirDiff` against those marked directories, but I'm not that familiar with Lua yet to write that. ;/

The open_on_setup feature apparently has been removed in nvim-tree.lua https://github.com/nvim-tree/nvim-tree.lua/wiki/Open-At-Startup. Look at this wiki page where you can get all the necessary helpful information there about how to configure open_on_setup.

My tabstop is changing from 4 to 8 everytime that I open a file using nvim-tree https://github.com/nvim-tree/nvim-tree.lua