tree-sitter-python VS neotest

(use-package treesit :ensure nil :custom ;; Some stuff taken from here: https://robbmann.io/posts/emacs-treesit-auto/ (treesit-extra-load-path '("/usr/lib64/")) (treesit-language-source-alist '((bash . ("https://github.com/tree-sitter/tree-sitter-bash")) (c . ("https://github.com/tree-sitter/tree-sitter-c")) (c++ . ("https://github.com/tree-sitter/tree-sitter-cpp")) (csharp . ("https://github.com/tree-sitter/tree-sitter-c-sharp")) (css . ("https://github.com/tree-sitter/tree-sitter-css")) (elixir ("https://github.com/elixir-lang/tree-sitter-elixir")) (html . ("https://github.com/tree-sitter/tree-sitter-html")) (java . ("https://github.com/tree-sitter/tree-sitter-java")) (javascript . ("https://github.com/tree-sitter/tree-sitter-javascript")) (json . ("https://github.com/tree-sitter/tree-sitter-json")) (lua . ("https://github.com/Azganoth/tree-sitter-lua")) (makefile . ("https://github.com/alemuller/tree-sitter-make")) (org . ("https://github.com/milisims/tree-sitter-org")) (python . ("https://github.com/tree-sitter/tree-sitter-python")) (tsx . ("https://github.com/tree-sitter/tree-sitter-typescript" "master" "tsx/src")) (typescript . ("https://github.com/tree-sitter/tree-sitter-typescript" "master" "typescript/src")) (ruby . ("https://github.com/tree-sitter/tree-sitter-ruby")) (rust . ("https://github.com/tree-sitter/tree-sitter-rust")) (sql . ("https://github.com/m-novikov/tree-sitter-sql")) (toml . ("https://github.com/tree-sitter/tree-sitter-toml")) (yaml . ("https://github.com/ikatyang/tree-sitter-yaml")))) (major-mode-remap-alist '((c-mode . c-ts-mode) (c++-mode . c++-ts-mode) (csharp-mode . csharp-ts-mode) (css-mode . css-ts-mode) (html-mode . html-ts-mode) (java-mode . java-ts-mode) (js-mode . js-ts-mode) (json-mode . json-ts-mode) (makefile-mode . makefile-ts-mode) ;; (org-mode . org-ts-mode) ;; not mature yet (python-mode . python-ts-mode) (typescript-mode . typescript-ts-mode) (ruby-mode . ruby-ts-mode) (rust-mode . rust-ts-mode) (toml-mode . toml-ts-mode) (yaml-mode . yaml-ts-mode))) (treesit-auto-fallback-alist '((toml-ts-mode . conf-toml-mode) (typescript-ts-mode . nil) (tsx-ts-mode . nil))) (treesit-font-lock-settings t) (treesit-simple-indent t) (treesit-defun-type-regexp t)) (use-package treesit-auto :demand t :config (setq treesit-auto-install t) (global-treesit-auto-mode))

i dont see the issue reported in the python parser: https://github.com/tree-sitter/tree-sitter-python/issues

How can we add different highlight for __dunder__ methods a.k.a. magic methods? Is there a TS highlight group for that? I know that in tree-sitter-python there is pythonTSConstructor for __init__ method that I can customize, but I couldn't figure out for other magic methods.

You could try elisp-tree-sitter as soon as this issue is closed.

My first neovim plugin project was to write an adapter (runner) for neotest, for a language that I use regularly and which was missing from the existing adapters.

There's overseer.nvim to run all sorts of things and neotest to run tests. In general, you can check awesome-neovim or TWiN to look for plugins.

Here's some things that may help: - https://github.com/mfussenegger/nvim-dap + dap ui - https://github.com/nvim-neotest/neotest

I use neotest to run tests (with pytest).

For testing I use https://github.com/nvim-neotest/neotest which gives a nice outline.

For those who don't know it, it's an adapter for neotest, a Neovim plugin that

You might look at how Neotest handles this, or even see if you can use/contribute to that project directly. It already has support for a fair number of languages at varying levels of maturity.

I am writing Python these days, and LSP + DAP + neotest give me 90% of what PyCharm would have given me. I don't know how well this works with Java, the latter two did not exist when I was still writing Java. The way I did it was use Neovim with jdt-ls to write code and IntelliJ for debugging. Debugging does not require switching between keyboard and mouse, so it was OK to me.

I'm sure that we could figure out a way to install rocks without luarocks, but it's still going to be an additional step with possible complications. Personally, I would rather just embed the library within my plugin like neotest does with xml2lua. The marginal cost of a slightly larger install is more than paid for by an easier install process and a guarantee that it works.