deadgrep
tree-sitter
Our great sponsors
deadgrep | tree-sitter | |
---|---|---|
11 | 62 | |
699 | 16,450 | |
- | 5.7% | |
4.4 | 9.8 | |
18 days ago | 3 days ago | |
Emacs Lisp | Rust | |
- | 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.
deadgrep
-
Ripgrep is faster than {grep, ag, Git grep, ucg, pt, sift}
Deadgrep (uses ripgrep and evil-collection has a binding) takes me to my happy place -
https://github.com/Wilfred/deadgrep
-
James Dyer: More flexible grepping with deadgrep
theres a package for this that’s god tier: deadgrep
-
advanced-search
this is cool too Wilfred/deadgrep: fast, friendly searching with ripgrep and Emacs
- What have you recently *removed* from your Emacs configuration?
-
Navigating an enormous code base
rg.el or deadgrep: Emacs interfaces to ripgrep, a grep-like tool that is very fast. This lets us search across a large number of files for a pattern of text. The disadvantage of searching for text is that if you are looking for the method called foo and there are hundreds of them that exist, it can be hard to know which one you really want. On the other hand, at the scale and complexity that you are talking about, I can imagine that more IDE-like tools just start failing.
-
If you have never used wgrep with rg.el to rename a function in several files, try it | that will blow your mind
Yes in this area (text search) there is many alternatives. Wilfred Hughes (author of deadgrep) has listed them in: https://github.com/Wilfred/deadgrep/blob/master/docs/ALTERNATIVES.md
-
ripgrep is fantastic | Emacs is fantastic | BOOM you get the fantastic rg.el
Anyone interested in this should also check out deadgrep: https://github.com/Wilfred/deadgrep
- Difftastic: A diff that understands syntax
-
Is there a magit-like interface for grep?
Deadgrep does this, IIUC (I use ripgrep.el instead, but I think deadgrep does something like what you want)
-
Alternatives to two swiper/counsel commands
deadgrep is an interface to ripgrep.
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.
- An incremental parsing system for programming tools
-
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
-
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
[2]: https://github.com/tree-sitter/tree-sitter/issues/1870
[3]: https://github.com/tree-sitter/tree-sitter/issues/224
-
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.
-
Detailed syntax highlighting
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.
What are some alternatives?
rg.el - Emacs search tool based on ripgrep
nvim-treesitter - Nvim Treesitter configurations and abstraction layer
consult - :mag: consult.el - Consulting completing-read
Visual Studio Code - Visual Studio Code
emacs-find-file-rg - Find file in current project using rg --files command
indent-blankline.nvim - Indent guides for Neovim
dumb-jump - an Emacs "jump to definition" package for 50+ languages
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]
Emacs-wgrep - Writable grep buffer and apply the changes to files
language-server-protocol - Defines a common protocol for language servers.
json-diff - Structural diff for JSON files
coc-explorer - 📁 Explorer for coc.nvim