markdown-preview.nvim VS mini.nvim

- preview markdown: https://github.com/iamcco/markdown-preview.nvim

Hello, I want use nvim because is very cool, but I don't understand if it's mandatory to have a plugin manager or not. I want install a markdown-preview plugin but as I see on the readme I can use only plugin managers to install the plugin. If I scroll down the readme I find the install instrusction "by hand". But there is written that I have to add:

Personally, I take notes in Markdown. As for screenshots, I link them accordingly, saving them in either a $HOME/Pictures/ directory or in my current working directory for easy access. I also use Markdown-Preview while writing and editing so I can view the rendered notes (if necessary) in my default web browser.

I 100% agree, its just that I couldnt find anything better. There are some markdown renderers (like this) and many utils to manage a zettel or other notes (check these), but the graph part seems to be the most evasive one (or maybe I overlooked it)

6) I've been using this plugin.

J'ai installé Markdown Preview for (Neo) vim, le plugin fonctionne lorsque je tape manuellement : markdownpreviewtoggle mais j'essaie de l'exécuter en utilisant

I use this plugin https://github.com/iamcco/markdown-preview.nvim

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