quarto-nvim-kickstarter VS mini.nvim

- 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

This is essentially a tagline of mini.move.

Just as the others suggested, oil.nvim solves this outta the box. I freaking love it (here my config in case ya need it). Apparently also mini.files handles this by default

You mean backwards seeking text objects? You can get those with mini.ai https://github.com/echasnovski/mini.nvim/blob/main/readmes/mini-ai.md

I would like to offer you to join me in saying late greetings to this autumn with a release of mini.nvim version 0.10.0. It is mostly about introducing three (quite feature full, dare I say) modules and minor updates of existing ones.

Last night I cleaned up all the dead code in my config and realised that mini.nvim has to be the single best plugin that I've used. I have a couple of other favourites but this collection has been so consistently good that I wanted to give some thanks to the juggernaut that is u/echasnovski! Thanks for all the work you plugin authors and core maintainers put in to make this editor what it is <3

For example: I spent a lot of time configuring file tree plugins to have the same sorting as VS Code, tweaking their icons, etc. But then I realized I barely used the file explorer at all, and now I'm super happy with the minimal approach of mini.files. I had similar experiences with other plugins that were just adding "fluff" instead of the functionality I was looking for.

Around two weeks ago I've announced the release of mini.files - a file explorer module of mini.nvim with column view navigation and "edit text to manipulate file system" design. This resulted into a great feedback from the community, much of which turned into new features.

A mini.ai textobject specification that you can use standalone