rofi VS Vim

You'll probably like rofi.

Also, I use this script so that Rofi will show my clipboard instead of the native klipper UI (because it's far less keyboard friendly). Normally the script works great, but the script chokes whenever I `dd` an empty line or a lone `\`, putting an empty entry on my clipboard, which the wrapper than assumes means I'm at the end of the list of clipboard entries.

Which rofi you run? The original one from https://github.com/davatorium/rofi (which is Xorg base, so it has to start XWayland) or the Wayland-based fork on https://github.com/lbonn/rofi?

OS: Arch Linux WM: Qtile Panel: Qtile bar Launcher: Rofi Notification Daemon: Dunst Terminal: Alacritty Shell: Zsh Compositor: Picom File Manager: Nemo Music Player: Spotify & ncmpcpp

I like rofi (super flexible, i also use it as a custom alt-tab option in openbox) and wofi is a nice option on wayland

Modi are covered in the documentation. They set what Rofi displays in its window. You can run Rofi from a keybind, or a module in Polybar, or by using click handlers. Extremely extensible and versatile. And a shit ton of fun to theme. :)

xwinmosaic: Having tried XMonad.Actions.GridSelect in the past, I found the 2-dimensional grid more confusing than useful because you cannot intuit where it would lay things out. I find Rofi to be more usable for window switching because it prioritizes text filtering. https://github.com/davatorium/rofi

There have been six releases of Vim _this week_. So, no, Vim is not "dead".

https://github.com/vim/vim/tags

Vim

We wanted this machine to be as lean as possible. There is only so much memory and processing power to go around. Remember, our machine has 3 GHz Dual-Core Intel Core i7 processor with 16 GB 1600 MHz DDR3 memory. We also wanted as much of that space and power to be used for serving up our web applications. However, we also wanted to have an additional option for editing any code files, in addition to vim.

Vim: winget install vim.vim

So Raylib library could be your best option. Let's code, just open your text editor like vim or VSCodium in your Windows, Linux or Mac computer and let's build our indie game with Raylib library, no extra dependencies are needed.

nevermind, after a little searching, I found the solution, this isn't 'a nvchad problem or neovim problem, but a vim problem, and this github issue explains it. In the bottom of the issue, someone did post a fix here, but I haven't really tried it.

Then I went to official vim GitHub and looked around and it also had only instruction for installing vim from scratch.

When you said Vim, I thought you were talking about Vim (a code editor). Clearly not haha