vertico VS affe

It would be great if you add your snippet to the Vertico wiki. Such tweaks can be quite instructive for others who want to achieve the same or similar effects for other completion commands.

If you want completion to be sorted by your "most recent" I suggest you have a look at completion libraries. One example is vertico; when you enable savehist mode, the variable magit-revision-history, containing the branches you visited is persisted between sessions and vertico use that offer completions by most-recently-used, by default.

I think vertico is best alternative recently, really fast on Linux, macOS and Windows.

(use-package modus-themes :vc (:url "https://gitlab.com/protesilaos/modus-themes" :branch "main")) (use-package vertico :vc (:url "https://github.com/minad/vertico" :rev :newest :lisp-dir "extensions/"))

An example relevant to your list would be some changes many people are taking with their completion framework - using package that leverage core emacs functionality rather than replacing it with a complete package that 'overrides' it. Consult, vertico, orderless and associate packages come to mind here. If you do a bit of a search you'll find plenty of info. Here is a video from Prot on the subject, but there are many others as well. I think Prot actually went on to write his own completion system to overlay native emacs functionality as well.

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).

Wow, interesting that my response is getting down voted. It seems not enough that I give away my work for free. Nevertheless I appreciate support from the community, as other Emacs package developers. The support is actually helpful. To clarify, publishing my configuration would translate into quite a bit of work, requiring separation of private and public bits.

I thought that lsp and rtags were different tools to do different things. Regarding lsp, I configured lsp-mode in my init file indeed! Currently I'm using Vertico (plus recommended sub-packages at github repository) and lsp-mode.

Hey! There has already been a horizontico.el. ;)

FYI, selectrum is getting deprecated in favor of vertico. https://github.com/minad/vertico/issues/237

and another one, from the author of consult/vertico/..., minad, is affe: https://github.com/minad/affe

Why does it not mention affe from u/minad-emacs? https://github.com/minad/affe

If you don't mind, I have a bit of an unrelated question for you: What are your thoughts on Emac's existing multithreading support? For a few weeks now, I'm trying to do something practical with them, and found that they at least enable one thing: accept-process-output can be done without blocking the main thread (I have an small example and I'm preparing a blog post). I'm asking because I stumbled upon this project of yours: https://github.com/minad/affe and thought that it would be easier to implement with threads (with all their limitations). It would require careful coding so that the heavier computations don't block or starve the main thread, but I think it's possible, and would result in smaller and more performant code.

I found [affe.el](https://github.com/minad/affe), but I don't want to add this package if doom supports this kind of feature.

The closest thing you're looking for is affe it just uses completing-read in an async manner. The filtering is also done async so there is no lag. It supports emacs' completion styles, e.g. you can couple it with orderless.

Affe provides an asynchronous fuzzy finder similar to the fzf command-line fuzzy finder, written in pure Elisp. A producer process is started in the background, e.g., find, fd or ripgrep. The output produced by this process is filtered by an external asynchronous Emacs process. The Emacs UI always stays responsive since the work is completely off-loaded to other processes. The results are presented in the minibuffer using Consult, which allows to quickly select from the available items.

You may want to try my Affe, the Asynchronous Fuzzy Finder for Emacs, which works similarly to fzf and is fast, since the file list is generated only once and the filtering is performed in an external process on all files. However there is also no support for flex sorting, only filtering as offered by orderless.