dired-hacks VS elisp-tree-sitter

I have used Clemeras dired-git-info for a while, but it does not work well with my dired-auto-readme and dired-subtree from dired-hacks due to use of overlays.

beacon which-key auto-package-update dired-hacks helm

As an alternative to do stuff manually as Prot does, you can also take a look at dired-hacks by Goljer, a.k.a Fuco, in particular dired-subtree and dired-filter. Dired-subtree let's you "toggle" directory listings displayed inline, similar as how other file managers expand/collapse directories in "list-mode". If you prefer using Dired interactively, that one is a game changer in my opinion. I have 'dired-subtree-toggle' on a tab key, so I can just quickly press tab to "expand/collapse" a folder. it is not same as pressing 'i' in Dired and having content of a directory inserted "below", but in my opinion, I never find the built-in Dired version very appealing. Subtree-toggle also skips extra headers for inserted directories, and I can still do all dired operations on directories as if they were inserted with built-in method that Prot demonstrates. I have also used dired-subtree-toggle to make three small functions on top of it to expand entire directory tree one folder at a time, all at once and to collapse them.

On a similar note, dired-ranger has some awesome copy/paste/move functions.

I personally use just Dired, styled with some addons and a simple script where I use dired-subtree to expand/fold subdirectories one level at the time. You can use dired-subtree to expand one directory at a time.

dired-subtree (from dired-hacks) - hit tab on a directory and expand/fold the subtree;

If you are using dired-hacks, it comes with something called dired-subtree.

Look at the original integration project https://github.com/emacs-tree-sitter/elisp-tree-sitter, before it was done inside Emacs 29+.

When tree-sitter is available you may extend expand-region with this one one https://github.com/emacs-tree-sitter/elisp-tree-sitter/issues/20 Works very nice for me. But simple matching pairs should be handled well by expand-region alone

That said, if you want a more complete experience with tree-sitter right now, there’s a 3rd party implementation with support for a lot more languages, and also automatically downloads all supported grammars. It’s available here: https://github.com/emacs-tree-sitter/elisp-tree-sitter

Just like there are multiple LSP implementations for emacs (lsp-mode, eglot, lsp-bridge), there are multiple tree-sitter implementations. The one recently included in emacs was never a standalone package, I believe (correct me if that’s wrong), but was created with the purpose of being included in emacs. You will need melpa to download the linked elisp-tree-sitter package (https://github.com/emacs-tree-sitter/elisp-tree-sitter), but not the built in one.

How am I going to even use the built-in one? I was using elisp-tree-sitter. I know I have to add grammar for different languages, but how? I have been searching for a while and still have no clue.

from github README.rst "Emacs package that provides a standardized framework for manipulating and navigating your source code using tree sitter's concrete syntax tree " -> https://github.com/mickeynp/combobulate

https://www.spacemacs.org/ with https://github.com/emacs-tree-sitter/elisp-tree-sitter then write a iterator/loop query for language(s) editing per https://tree-sitter.github.io/tree-sitter/syntax-highlightin...

tad less installation heavy (sorta) but also makes use of tree-sitter syntax queries : https://www.lunarvim.org (neovim with treesitter syntax)

blockman usage examples: https://www.youtube.com/channel/UC5539gDeAdWqeXcczWuhnBA

Alternative examples / takes (per user interface):

### embedding a block of source code in a document:

  ** carrotsearch.gethub.io/apidocs/code-blocks

However, if you want to use tree-sitter today, there is the tree-sitter package which enables tree-sitter syntax highlighting in a number of popular major modes. I’ve been using it for about six months now in all major modes it supports.

Tree Sitter and lsp-mode might be of help. Looks like both take a bit of work to get going. I have personally not used them, so try out which suits you and let us know how it went.

You can use tree-sitter already if you have dynamic module support: https://github.com/emacs-tree-sitter/elisp-tree-sitter