telescope-file-browser.nvim
tree-sitter
Our great sponsors
telescope-file-browser.nvim | tree-sitter | |
---|---|---|
47 | 62 | |
1,467 | 16,106 | |
5.9% | 8.1% | |
7.5 | 9.8 | |
9 days ago | 2 days ago | |
Lua | Rust | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
telescope-file-browser.nvim
-
What are the plugins/settings to be able to view individual file or folder contents while scrolling through files or folders?
EDIT: I found what I was looking for https://github.com/nvim-telescope/telescope.nvim and https://github.com/nvim-telescope/telescope-file-browser.nvim
-
Telescope: how to search project directory?
an alternative is to use telescope-file browser, which simply allows you to interactively go up/down a directory: https://github.com/nvim-telescope/telescope-file-browser.nvim
- Is this Neovim?
-
Nvim + Moonlander: <3
I use a lot of key bindings for telescope. A regular use of mine is to open telescope file browser with `` without a previewer, and `` (shift) with previewer. So I have `Layer + f` that sends `` on tap and `` on double tap. Same goes for telescope grep string, but a different config: `` does a live grep in relative folder and `` does a global live grep. Very useful when navigating big monorepos. This is how the layer looks:
-
Terminal filemanager that works good with neovim
There's telescope-file-browser.nvim
-
People who migrated from vscode
hop.nvim to easily hop to specific text with minimal keystrokes
- veil.nvim - dynamic, component-based startup screen
-
Am I missing something with "move file" in neotree?
True that, relative path makes sense. But I think I will install again https://github.com/nvim-telescope/telescope-file-browser.nvim
-
Using neovim without a file tree plugin
there's also telescope-file-browser so you can still have a file tree but you can fuzzy find over it.
Whenever I need a file browser I use https://github.com/nvim-telescope/telescope-file-browser.nvim (mapped to fb), but I most often use ff which is mapped to telescope find_file.
tree-sitter
-
Lezer: A Parsing System for CodeMirror, Inspired by Tree-Sitter
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...)
-
Difftastic, a structural diff tool that understands syntax
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...
-
Effective Neovim Setup. A Beginner’s Guide
This is a plugin that provides a simple way to use the tree-sitter in Neovim and also provides functionalities like highlighting, etc.
-
Topiary: A code formatting engine leveraging Tree-sitter
From the tree-sitter side, I am tracking https://github.com/tree-sitter/tree-sitter/issues/1942
We rely on the Rust bindings from the main tree-sitter repository on the C library. Loading and matching the queries on the source file is done by this library, and so out of scope for Topiary.
-
Shiki Syntax Highlighter
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
Tree-sitter is going to be a lot slower to load: https://github.com/tree-sitter/tree-sitter/issues/1942.
It's ok for things like editor but using it in a SSG for example is hard when just loading the syntaxes will take multiple times the time it takes to render the whole thing with a regex based highlighter.
-
It seems that some BIG improvements of Treesitter on BIG FILEs have been merged into Nightly! (minutes ago!)
u/lewis6991 I think the biggest performance gain was made by tree-sitter itself: https://github.com/tree-sitter/tree-sitter/pull/2085
-
Looking for Tree-sitter query documentations and guides
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).
-
Will Treesitter ever be stable on big files?
The following discussion here. TS query cannot be incremental, that is why I regard it as design fault.
What are some alternatives?
nvim-tree.lua - A file explorer tree for neovim written in lua
nvim-treesitter - Nvim Treesitter configurations and abstraction layer
neo-tree.nvim - Neovim plugin to manage the file system and other tree like structures.
Visual Studio Code - Visual Studio Code
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
indent-blankline.nvim - Indent guides for Neovim
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]
language-server-protocol - Defines a common protocol for language servers.
coc-explorer - 📁 Explorer for coc.nvim
nvim-lua-guide - A guide to using Lua in Neovim
sourcegraph - Code AI platform with Code Search & Cody
lir.nvim - Neovim file explorer