elisp-tree-sitter VS .emacs.d

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

In my Helm, I have to actively choose the candidate to confirm it. So I can type in both paths that are shorter or longer then existing ones. I even made a video to demonstrate it, the thread was relatively recently up I think. My Helm setup is here it if helps you, find Helm in the list of packages.

I also use Helm, and I have no problems. Just keep typing, once you typed a letter that does not exist in a path name it will stop completing. I don't know if I have some special option enabled/disabled; I don't think you need it, but you can see my Helm config (just scroll down untill you find "Helm").

When all deps are installed,my config is over 200 packages. On my Arch Linux desktop I built in 2016, with i7 4.6k (haswell) it starts ~0.7 secs, but init time will be anything between 0.5 ~ 0.8 secs, i guess depending on what system does. So all things same, init time will vary.

I am using it in my literate org-config. If you scroll down, there is a big list of packages, and I have done a small wrapper around helm-imenu, to jump to a package configuration. Looks like this.

That does not work for completions, at least not for me. It works for keymaps, so you can have mode specific (or really any) keymap in src blocks. I have been using his method myself in my init file generator for quite a while now. If you (or anyone) knows/have an idea how to expand it for completions and eldoc, I would be really happy to hear.

I don't know what if it is more robust but I use more or less plain dired with just some options turned on to make it less noisy to look at, but I don't "manage" my files so much to be honest. I do use some extras from dired-hacks, and my own dired-auto-readme, but that is about it. You can check my setup if you wish, look at "dired" under packages and in Lisp folder for "dired-extras.el".

I personally put all custom lisp in a special directory and scrape autoloads myself. If you are curious, you can check under "generator", functions generate-autoloads and collect-autoloads, but there is nothing special, just plain text search and copy-paste programmatically. I don't recommend to use it though.