bufferline.nvim VS mini.nvim

So, I'm using bufferline and I want to setup some highlight colors based on the current Neovim theme (light or dark). While Neovim is working, if I run :lua print(vim.o.background) effectively gives me light or dark according to the current Neovim theme. BUT, doing so in the plugin's configuration does not work:

if you use bufferline you can override with: lua options = { offsets = { { filetype = "NvimTree", text = "File Explorer", text\_align = "center" } } }

I’m not familiar with Nvchad but I’m sure they’re using some kind of plugin that show buffers as tabs, you could try something like bufferline.nvim

there are many ways to achieve that. i recommend bufferline.

🧩 Works with any plugin. Check Show and Tell for snippets to integrate even better with plugins like neo-tree.nvim, bufferline.nvim

Left and right arrows to switch between buffers. I used to pair this with giving every buffer its own tab, but now I just use Bufferline which functions similarly.

I'm currently using bufferline.nvim with scope.nvim. I made a github repo with the modifications and credits to Everblush, but I'm not sure if it's allowed, since Everblush doesn't have a License. If It's not allowed, then I'll just delete the repo and forke the Everblush repo.

I used bufferline https://github.com/akinsho/bufferline.nvim

I believe this bug was fixed in bufferline.nvim's PR#727.

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