dotfiles VS nvim-treesitter-textobjects

To take full advantage of what JDTLS has to offer, you need to create a file in your config directory called ftplugin/java.lua. The ftplugin is a directory to handle filetype specific configurations. And if you're using Linux, you're in luck, because you can use mine. If you're using another OS, you have to make some tweaks.

Other than what I've shown you, I also use vscode's launch.json, which nvim-dap can load (I don't hard-code my DAP configs). If you want, you can take a look at the rest of my setup here: https://github.com/igorlfs/dotfiles/blob/main/nvim/.config/nvim/lua/plugins/nvim-dap.lua

Hey, I'm not using lazyvim, but my config is pretty similar, and I've got you covered with test and a REPL: https://github.com/igorlfs/dotfiles (it's also possible to enable typechecking but I'm not using it rn)

You can check my dotfiles if you want a peek on how to configure these plugins :P

Hey, I mostly develop python, and I'm pretty fine with my own setup: https://github.com/igorlfs/dotfiles. Supports LSP, Debugging, Jupyter integration and all the fancy things

You can use my config as an inspiration: https://github.com/igorlfs/dotfiles More specifically: https://github.com/igorlfs/dotfiles/blob/c961931f35a969b408fa8292b4c52cd9b76ad486/nvim/.config/nvim/lua/plugins/lsp.lua#L111

Sure! You can find my config here: https://github.com/igorlfs/dotfiles

I was hoping to use nvim-treesitter-textobjects to jump to the next argument via something like this:

You want to look at nvim-treesitter-textobjects. It let's you define keymaps for navigating text objects defined by treesitter and you can also use them with commands like d, c and so on.

Thank you! It looks like nvim-treesitter-textobjects is a good plugin to start with:

https://github.com/nvim-treesitter/nvim-treesitter-textobjec...

I'm aware of nvim-treesitter-textobjects and I suspect my answer lies in this plugin, but is there a way to move between root nodes that is agnostic of the node type?

Thanks! I just started using https://github.com/nvim-treesitter/nvim-treesitter-textobjects, and it works as a charm.

nvim-treesitter-textobjects

In this case, reading here is probably a good start: https://github.com/nvim-treesitter/nvim-treesitter-textobjects

Have a look at https://github.com/nvim-treesitter/nvim-treesitter-textobjects. Set up the @block.inner and @block.outer textobjects and it should work.

nvim-treesitter-textobjects lets you jump to (for instance) functions more accurately than with a regex-based approach using ]f

Or even better, one can use nvim-treesitter-textobjects. It already provides function/class selection and go-to functionality out-of-the-box.