hologram.nvim VS mini.nvim

Awesome! What's the difference between this and hologram? Would you like to support sixel so that it can be used in other terminals like alacritty?

hologram doesn't work for you? Although, there's a bit of an issue with images disappearing and to get them back I have to replace a character in the image's link.

There are some plugins to display images in nvim (edluffy/hologram.nvim), but it depends on the terminal and graphic protocol you use

kitty terminal can show image https://github.com/edluffy/hologram.nvim but i use peek.nvim to preview markdown

Hi good stuff! Is there any plans for hologram.nvim integration?

Nope, I used the hologram.nvim plugin to display the images, and it uses the kitty graphics protocol. That is why it only works with kitty.

The images can be drawn anywhere on the screen. Drawing inside an editor isn't too much work but requires some bookkeeping to handle scrolling, cropping and windows closing. See https://github.com/edluffy/hologram.nvim for an example of what is possible.

Im actually using hologram.nvim integrated with neorg (it only works in kitty + pngs for now)

Basic image manipulation/preview. This includes: 1) the ability to call external tools (draw.io/inkscape, etc) for simple image creation and insertion on the fly 2) removing an image link from markdown also removes the corresponding file 3) file preview inside neovim buffer. I just discovered a plugin that make this possible: hologram.nvim, has anyone tried it out?

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