dotfiles VS combobulate

I think it's beneficial to write these files in the normal way and then just add them to the store with simple home-services through local-file (plain-file is ok too but messier in my opinion). Its easier to understand, removes a point of failure in the scheme configuration -> normal configuration step, portable, "immutable", and it allows you to collect them all into one nice dotfiles repo. Here's mine for an example: https://github.com/Tass0sm/dotfiles/tree/master/home/files

I use Guix Home for managing my dotfiles on Arch Linux. I think its pretty fun but its not totally perfect. This config also isn't totally reproducible. Here's the link for that repository: https://github.com/Tass0sm/dotfiles

Eh, I've been looking and haven't found anything for other editors that actually tries to use TreeSitter for anything beyond highlighting. The Emacs structural editing packages are still very WIP but at least they exist.

(And also some have been based on the out of tree implementation that's been around for a while now)

Example: https://github.com/mickeynp/combobulate

Looking at https://github.com/mickeynp/combobulate/blob/master/combobulate-python.el, it at the very least delegates to python-indent-calculate-levels, so the logic is mixed.

I went from an old config rich setups from before lsp's to lsp-mode ones etc... Right now I would say that eglot + pylsp gives you the best experience, you can use pyenv and pyvenv mode to manage your virtual environments. Now that treesitter is also being used you can try out https://github.com/mickeynp/combobulate

I think the following packages would fit your wishlist, as it is very similar to mine. As mentioned in the replies, there is (https://github.com/magnars/expand-region.el) and (https://github.com/mickeynp/combobulate). I regularly use (https://github.com/Fuco1/smartparens).

re syntactic text objects: https://github.com/mickeynp/combobulate

I haven't used it, but based on the description, it looks like combobulate would be an example of this:

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

I don't know what this fork brings to table, but you could try tree-sitter today with your vanilla Emacs using a package[1] that works via dynamic module.

Personally I am more interested in getting structural selection and navigation reliably working for any language. There is also a package named combobulate[2] to help with that.

[1] https://emacs-tree-sitter.github.io/

[2] https://github.com/mickeynp/combobulate

TIL https://github.com/mickeynp/combobulate Thank you, @snafuchs !