icomplete-vertical VS .emacs.d

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.

In my Helm, I have to actively choose the candidate to confirm it. So I can type in both paths that are shorter or longer then existing ones. I even made a video to demonstrate it, the thread was relatively recently up I think. My Helm setup is here it if helps you, find Helm in the list of packages.

I also use Helm, and I have no problems. Just keep typing, once you typed a letter that does not exist in a path name it will stop completing. I don't know if I have some special option enabled/disabled; I don't think you need it, but you can see my Helm config (just scroll down untill you find "Helm").

When all deps are installed,my config is over 200 packages. On my Arch Linux desktop I built in 2016, with i7 4.6k (haswell) it starts ~0.7 secs, but init time will be anything between 0.5 ~ 0.8 secs, i guess depending on what system does. So all things same, init time will vary.

I am using it in my literate org-config. If you scroll down, there is a big list of packages, and I have done a small wrapper around helm-imenu, to jump to a package configuration. Looks like this.

That does not work for completions, at least not for me. It works for keymaps, so you can have mode specific (or really any) keymap in src blocks. I have been using his method myself in my init file generator for quite a while now. If you (or anyone) knows/have an idea how to expand it for completions and eldoc, I would be really happy to hear.

I don't know what if it is more robust but I use more or less plain dired with just some options turned on to make it less noisy to look at, but I don't "manage" my files so much to be honest. I do use some extras from dired-hacks, and my own dired-auto-readme, but that is about it. You can check my setup if you wish, look at "dired" under packages and in Lisp folder for "dired-extras.el".

I personally put all custom lisp in a special directory and scrape autoloads myself. If you are curious, you can check under "generator", functions generate-autoloads and collect-autoloads, but there is nothing special, just plain text search and copy-paste programmatically. I don't recommend to use it though.