orderless VS icomplete-vertical

orderless. A highly configurable completion style that matches multiple patterns in any order against minibuffer completion candidates.

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.

You didn't mention, so I'll ask, are you using the orderless (https://github.com/oantolin/orderless) completion style?

Fuzzy completion ala Orderless would be awesome: hitting space during completion acts as a pattern separator.

I dunno—I like how Vertico+Counsel feel. I'm not sure how good the support for Orderless and Embark are in Ivy, but I really like how those packages compose so nicely with the Vertico+Consult ecosystem.

In general, you want either orderless or prescient, with my personal preference being the former.

You probably want to investigate completion styles. There are many builtin styles, from basic, which just does prefix completion, on up. But there are also 3rd party styles. One of the most powerful is called orderless. Considering all these styles, there really is a ton of flexibility in how you can get to a completion candidate like some-named-something (some, s-n-s, sns, soso, [a-z]{4}-na, e\b \bs, ...). You can even configure more than one style at a time (and usually do).

Well, I've written some general purpose Emacs packages (orderless and embark) that I use a lot, but I also write Emacs Lisp for one-off tasks.

I like it. Would be nice to see orderless-style (https://github.com/oantolin/orderless) completion, and a config not to enter the directory by narrowing the completion to one, requiring enter to be pressed.

You can display icomplete/fido vertically if you like that better with (setq icomplete-separator "\n") or with https://github.com/oantolin/icomplete-vertical

I don't use icomplete nor vertico most of the time, but I am very familiar with them. I've tried lots of completion UIs: default completion, ido (with ido-completing-read to get it everywhere), icomplete, vertico, selectrum, helm, ivy; and I've written several myself: icomplete-vertical, live-completions, grille, embark-collections-completions.

Helm commands only work in Helm. Ivy and Counsel commands only work in Ivy. Consult commands work in Selectrum, Vertico, Icomplete Vertical, and maybe some other interfaces. That's all I meant. Of course, that only matters if you don't wish to use Helm or Ivy.

Consult supports asynchronous candidate sources now! This allows to implement grep and find commands which update the candidate lists while you type. Consult is made to work well with the default completion system, Selectrum and Icomplete-vertical.