doomemacs/modules/completion
Henrik Lissner 6f40ad55f5
docs: discourage after! and use-package! use
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.
2026-02-09 04:29:47 -05:00
..
company docs: discourage after! and use-package! use 2026-02-09 04:29:47 -05:00
corfu docs: discourage after! and use-package! use 2026-02-09 04:29:47 -05:00
helm docs: discourage after! and use-package! use 2026-02-09 04:29:47 -05:00
ido fix: file-name-concat paths instead of concat 2025-12-30 22:59:10 -05:00
ivy docs: discourage after! and use-package! use 2026-02-09 04:29:47 -05:00
vertico bump: :completion 2026-01-06 02:00:17 -05:00
.doommodule feat: add .doommodule files 2024-09-14 20:47:39 -04:00
README.org revert: fix(docs): set mode in file-local vars 2022-08-07 19:08:07 +02:00

: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.