swiper VS rofi

This is a good improvement. Personally though I left isearch behind. For further search convenience / functionality I highly recommend swiper.

Next you "only" have to remember (elisp) function names. "Completion UIs" like ivy/counsel, icomplete, helm or vertico/consult, give you a nice auto completion list on M-x (choose the one of them, you like the most). Some of those Completion UIs will display existing keybindings and a short documentation for commands, near the auto complete candidates. So you will start to remember more keybindings without "learning sessions", just because invoking functions via keybindings is much faster (more convenient).

Proposal 4 (group-function). This one is an actual addition, which allows candidate gouping in the style of Helm. Note that it is a pure addition. Completion UIs and completion packages work perfectly fine without it. It wouldn't be difficult to add support to Ivy. I wrote the patch.

For the unfamiliar, Swiper is a part of Ivy which lets you search through your buffer with a preview of match candidates: you type some text you're looking for, and up pops a list of matching lines in the minibuffer that you can then use the arrow keys, C-n C-p etc. to scroll through and select the one you want.

When I started using Emacs I was following the setup outlined by System Crafters, which I still think is a really good introduction. But, over the last few months I've started to replace packages with more "minimalist" or "stripped down" packages. I've switched from Ivy and Counsel to Vertico and Consult, and recently I switched from company to corfu for auto-completion.

Ah, neat. I hadn't considered appending comments for searchability. I'm currently getting searchabiity from M-x dwim-... and ivy completion.

Great question. I have one big file with a few hundreds book and quotations from them. Problem is with newlines. When I copy text from kindle it doesn't have newlines because it's depends on font size. So every quotation from book is on one line - could be few thousands chars. I use visual-line-mode and there is a big problem with that. Like swiper would just freeze your emacs if you try to search. https://github.com/abo-abo/swiper/issues/925 Anyone have same problem?

Today is a lazy Sunday, and I did what nobody should do on a Sunday: Spend time trying to replace something that already works. This time, my victim was rofi.

I still use QuickSilver on my mac, despite there are multiple efforts attempting to displace it. There used to be one made for Linux, called Gnome Do, however the development eventually stopped. I settled for the built-in launcher in Gnome Shell, and then briefly moved on to rofi with this configuration.

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