763464afdb
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`. It's supposed to add the advice by itself, but it's very unreliable, so we do the wrapping manually. Ido doesn't implement `completion-in-region` and its `completing-read` is retricted to a list of strings as table, so we use default `completion--in-region` with no bells or whistles. |
||
|---|---|---|
| .. | ||
| 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.