move.nvim VS bufferline.nvim

there is also move.nvim which also allows you to move a visual block like that: https://github.com/fedepujol/move.nvim

The author of move.nvim has inactive his repo (https://github.com/fedepujol/move.nvim) and now this plugin comes, thanks so much <3

I've just updated my plugins and noticed that fedepujol/move.nvim was giving me an error.

I was trying to find a clean, concise way to set up my mappings through legendary.nvim for move.nvim which has separate commands for normal vs. visual mode. I didn't want a separate line for each mode (which before would be needed because different commands would be run based on the mode).

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.