grapple.nvim VS buffer_manager.nvim

There's also grapple.nvim which is similar, but with a stronger focus on "marking"

Last week I posted about a full rewrite of Portal.nvim. Along with several new features, it became far easier to tie in with existing lists. So, today I wanted to showcase a couple new builtins: integrations with grapple.nvim and harpoon!

I prefer specifying a set of files and cycling between them. Plugins like grapple.nvim or harpoon are great for easily switching between a few project-specific files.

That was a good reminder for me to update grapple.nvim! A couple notes about the showcase:

Repo: https://github.com/cbochs/grapple.nvim

I received lots of great feedback on an experimental plugin that I showcased recently called cbochs/grapple.nvim. It got me thinking about what I was really trying to achieve with grapple.nvim and how it would differentiate itself from existing plugins (e.g. harpoon).

Custom lualine component (from showcase): https://github.com/cbochs/grapple.nvim/wiki/Lualine

I like to use buffer_manager, for my buffers.

I really enjoy https://github.com/j-morano/buffer_manager.nvim

https://github.com/j-morano/buffer_manager.nvim is a nice one.

A little over two weeks ago, I wrote a post about a simple plugin I created to manage buffers in Neovim: buffer_manager.nvim. After the feedback received, I have added a few features proposed by some users that I consider quite useful:

Context: I'm still pretty new to Neovim, setting up Plugins without strong documentation is still steep for me but this seems like a gentle introduction that will teach me a lot. I am trying to install and use buffer_manager.nvim