swiper VS fzf

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?

I've been frustrated with how slow terminal filesystem navigation feels in comparison with modern apps like Notion, Slack, Discord, etc.

I discovered the amazing https://github.com/junegunn/fzf , and realized I could build ⌘-k for the terminal.

In my blog post yesterday, I mentioned fzf. Its simplicity and power make it a good tool for many scripting tasks. In this post, we will see a practical example of how to use it in a CLI program and package it with Nix.

But also, sway-launcher-desktop is a brilliant hack that uses fzf to implement a launcher that works in the console. I can think of many such use cases. As a starting point, I revisited my fzf shell integration configuration today and decided to invest in it a bit more for my scripting efforts.

fzf GitHub

fzf is a command-line fuzzy finder that makes navigating through files, commands, and processes much easier. It's kind of like ctrl + P on vscode, but for your terminal

Install "fzf" [0] and set it up to be used with control+r, there's no going back. You get as a bonus the chance to use fzf in a lot of other places :)

I guess that more advance tool would be "atuin" [1], but it is too much for my use case.

[0] https://github.com/junegunn/fzf

FZF is a command line fuzzy finder. It's an incredibly powerful tool that you can use (at its simplest) to filter lists as you type.

fzf (fuzzy finder)

fzf