956b85310c
We previously implemented only consult/vertico as a target for export, now we have all of them. It was necessary to use case-by-case conditions, unfortunately, because other UIs have subtle quirks that prevent a single generalized approach to work. Ivy is almost compliant, but it needs beg and end to not be markers. Helm doesn't replace `completion-in-region-function`, it expects to go around the default `completion--in-region`, so a small addition was made to its module, because we weren't doing that. This was likely an oversight due to the non-standard usage. This was fixed here because we need it working for this feature. Ido doesn't implement `completion-in-region` and its `completing-read` is retricted to a list of strings as table, so it's treated the same as absence of a framework, because it lacks the needed features. |
||
|---|---|---|
| .. | ||
| company | ||
| corfu | ||
| helm | ||
| ido | ||
| ivy | ||
| vertico | ||
| README.org | ||
:completion
Description
These modules provide interfaces and frameworks completion, including code completion.
Frequently asked questions
Should I choose Ivy, Helm, Vertico, or Ido?
Vertico is Doom's default and comes highly recommended of the four. It is the fastest, best integrated in Doom's ecosystem, and its module is the most actively maintained of the four. It also has the cleanest codebase and ties into native functionality already existing in Emacs, rather than reinventing the wheel.