quarto-nvim-kickstarter VS nvim-treesitter-textobjects

- https://github.com/jmbuhr/quarto-nvim-kickstarter

I view otter.nvim more as a library with tools to use in your config or other plugins. It extract's the code chunks, keeps the otter buffers in sync, provides a nvim-cmp source for completion and forwards modified LSP requests. quarto-nvim on the other hand is specific to quarto documents. So it provides some keybindings to otter functions and sets up the otter.nvim source in the example configuration I provide (https://github.com/jmbuhr/quarto-nvim-kickstarter), but also does things like `quarto preview`.

Are you using treesitter? I think it only defines regular paragraphs and headings as spelling regions (see @spell here: https://github.com/nvim-treesitter/nvim-treesitter/blob/master/queries/markdown/highlights.scm). You can add your own query to make another region spell check as well by adding a file to your config like this (example is for the R filetype, same principle for markdown): https://github.com/jmbuhr/quarto-nvim-kickstarter/blob/main/after/queries/r/highlights.scm in which you then add @spell to a query. Check out nvim-treesitter-playground to find the query you need.

For quarto and plain code files I am still on vim-slime, either using a terminal buffer or a tmux pane. If you find a more neovim centered solution, do let me know in an issue over at https://github.com/jmbuhr/quarto-nvim-kickstarter ;)

Here are some examples: https://github.com/jmbuhr/quarto-nvim-kickstarter/blob/main/lua/plugins/treesitter.lua

To edit code in a quarto document you can use my quarto-nvim plugin: https://github.com/quarto-dev/quarto-nvim and get a headstart of plugins that complement it here: https://github.com/jmbuhr/quarto-nvim-kickstarter

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.