nvim-cokeline VS nvimux

I'm trying to use it to render it in a cokeline component, I want to hide only the very first letter when I'm picking a buffer, so I can show the pick_letter instead. Everytime the filename starts with one of those special multibyte characters (pretty much never), the buffername gets a weird character.

Cokeline (bufferbar) to see which buffers are loaded and close the ones i don't need

I've looked at Heirline a few times but I just can't get past not really understanding why I would use this over other tablines. There are a metric shitload of possibilities but I am a simple man. The lack of images on the repo makes it difficult for me as a perspective user, to look at the repo and decide if I want to use this or not. Given that Heirline is focused around a UI piece of neovim, whats your thoughts on getting a sort of "Gallery" put together to show what can be done with Heirline? Something akin to how cokeline.nvim or barbar.nvim handles this?

They is me :) I use cokeline

New merge to master that now provides support for is_first and is_last components

May I interest you in some?

Hi everyone! I recently switched nvim-cokeline to semantic versioning and v0.1.0 has been released a few days ago. The plugin has had a ton of improvements since my last post, just to name a few:

My main goal at this stage is to get as many people as possible to check out the project and give feedback for further development. If you're currently using some plugin that offers similar functionality, consider checking cokeline.nvim out!

Check it out at noib3/cokeline.nvim!

Check it out on noib3/cokeline.nvim and let me know if you like it! Feedback is greatly appreciated :)

This looks great. I had a few issues with neovim and tmux at the same time, it causes me mental friction because I'm constantly having to check whether I'm in neovim or tmux terminal. That's why I created nvimux. Nonetheless, excellent job!

If you use nvimux, you can configure new splits to open terminals by default.

So, yes, there are a few differences. My goal is to have something I can run my tests for plugins like nvimux and iron.nvim, so it could've been any of the ones you mentioned, yes. But also, I really like this data-oriented approach and I felt like trying and writing something. Might be beneficial to more people than just me.

There's a neovim plugin for that (hkupty/nvimux), but I haven't tried it.

If you want to keep the same experience of using tmux inside neovim, check out nvimux. It keeps the same keybindings, using neovim terminal.

I've finally took some time to focus on dusting and fixing some code and I found a lot of possible improvements to nvimux. If you're excited to try, [it's on this PR](https://github.com/hkupty/nvimux/pull/41)