mirror of
https://github.com/doomemacs/doomemacs.git
synced 2026-03-09 08:11:12 -07:00
There's little reason for users to use these macros in their private configs over plain ol' `with-eval-after-load` and `use-package`, unless they're writing their own modules. It's my fault for signal boosting them in documentation and whenever I'm asked for help, because beginners now believe they are somehow required for Doom to work correctly (there are guides out there telling beginners that migrating to Doom involves replacing all instances of `with-eval-after-load` and `use-package` in their pre-existing configs with `after!` and `use-package!` -- which was never true). What's more, I plan to replace `use-package`, internally, so the `use-package!` macro won't exist for much longer. |
||
|---|---|---|
| .. | ||
| company | ||
| corfu | ||
| helm | ||
| ido | ||
| ivy | ||
| vertico | ||
| .doommodule | ||
| 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.