doom-emacs/modules/completion/corfu

:completion corfu

• Description
  • Maintainers
  • Module flags
  • Packages
  • Hacks
  • Changelog
• Installation
• Usage
  • Commit preview on type
  • Commit on RET with pass-through
  • Cycle directionally
  • Cycle with TAB
  • Searching with multiple keywords (+orderless)
  • Exporting to the minibuffer
• Configuration
  • Turning off auto-completion
  • Adding CAPFs to a mode
  • Adding CAPFs to a key
• Troubleshooting
• Frequently asked questions
• Appendix

Description   unfold

This module provides code completion, powered by doom-package:corfu.

It is recommended to enable either this or doom-module::completion company in case you desire pre-configured auto-completion. Corfu is much lighter weight and focused, plus it's built on native Emacs functionality, whereas Company is heavy and highly non-native, but has some extra features and more maturity.

If you choose Corfu, we also highly recomend reading its README and cape's README, as the backend is very configurable and provides many power-user utilities for fine-tuning. Only some of common behaviors are documented here.

Maintainers

• @LuigiPiucco
• @LemonBreezes

Become a maintainer?

Module flags

+icons

Display icons beside completion suggestions.

+orderless

Pull in doom-package:orderless if necessary and apply multi-component completion (still needed if doom-module::completion vertico is active).

+dabbrev

Enable and configure doom-package:dabbrev as a close-to-universal CAPF fallback.

Packages

• doom-package:corfu
• doom-package:cape
• doom-package:nerd-icons-corfu if doom-module::completion corfu +icons
• doom-package:orderless if doom-module::completion corfu +orderless
• doom-package:corfu-terminal if doom-module::os tty
• doom-package:yasnippet-capf if doom-module::editor snippets

Hacks

No hacks documented for this module.

TODO Changelog

This module does not have a changelog yet.

Installation

Enable this module in your doom! block.

This module has no direct requirements, but some languages may have their own requirements to fulfill before you get code completion in them (and some languages may lack code completion support altogether). Run $ doom doctor to find out if you're missing any dependencies. Note that Corfu may have support for completions in languages that have no development intelligence, since it supports generic, context insensitive candidates such as file names or recurring words. Snippets may also appear in the candidate list if available.

TODO Usage

🔨 This module's usage documentation is incomplete. Complete it?

By default, completion gets triggered after typing 2 non-space consecutive characters, by means of C-SPC at any moment or TAB on a line with proper indentation. Many styles of completion are documented below, which can be composed to suit the user. The following keybindings are generally available:

Keybind	Description
C-n	Go to next candidate
C-p	Go to previous candidate
C-S-n	Go to next doc line
C-S-p	Go to previous doc line
C-S-s	Export to minibuffer
TAB	(when not completing) Indent or complete
C-SPC	(when not completing) Complete
C-u	(evil) Go to next candidate page
C-d	(evil) Go to previous candidate page
C-h	(evil) Toggle documentation (if available)
M-t	(emacs) (when not completing) Complete

Bindings in the following sections are additive, and unless otherwise noted, are enabled by default with configurable behavior. Additionally, for users of evil, C-SPC is smart regarding your state. In normal-like states, enter insert then start corfu; in visual-like states, perform evil-change (which leaves you in insert state) then start corfu; in insert-like states, start corfu immediatelly.

Commit preview on type

When the completion popup is visible, by default the current candidate is previewed into the buffer, and further input commits that candidate as previewed (note it does not perform candidate exit actions, such as expanding snippets).

The feature is in line with other common editors, but if you prefer the preview to be only visual or for there to be no preview, configure var:corfu-preview-current.

;; Non-inserting preview
(setq corfu-preview-current t)
;; No preview
(setq corfu-preview-current nil)

Commit on RET with pass-through

A lot of people like to use RET to commit, so here we bind it to Corfu's insertion function. Note that Corfu allows "no candidate" to be selected, and in that case, we have a custom binding to quit completion and pass-through. To make it less obtrusive by default, the popup starts in this unselected state. See var:corfu-preselect to alter the initial behavior; it can start with the first one selected, for instance. Then, you have to move one candidate backwards to pass-through The exact action of RET can be changed via var:+corfu-want-ret-to-confirm.

Keybind	Description
RET	Insert candidate DWIM

Cycle directionally

If you'd rather think in directions rather than next/previous, arrow keys and vi movements to control the selection and documentation view are bound by default. You may unbind them by setting to nil, see map!'s documentation.

Keybind	Description
<down>	Go to next candidate
<up>	Go to previous candidate
C-j	(evil) Go to next candidate
C-k	(evil) Go to previous candidate
C-<down>	Go to next doc line
C-<up>	Go to previous doc line
C-S-j	(evil) Go to next doc line
C-S-k	(evil) Go to previous doc line

Cycle with TAB

TAB-based cycling alternatives are also bound according to the table below:

Keybind	Description
TAB	Go to next candidate
S-TAB	Go to previous candidate

Searching with multiple keywords (+orderless)

If the doom-module::completion corfu +orderless flag is enabled, users can perform code completion with multiple search keywords by use of space as the separator. More information can be found here. Pressing C-SPC again while completing inserts a space as separator. This allows searching with space-separated terms; each piece will match individually and in any order, with smart casing. Pressing just SPC acts as normal and quits completion, so that when typing sentences it doesn't try to complete the whole sentence instead of just the word. Pressing C-SPC with point after a separator escapes it with a backslash, including the space in the search term, and pressing it with an already escaped separator before point deletes it. Thus, you can cycle back if you accidentaly press more than needed.

Keybind	Description
C-SPC	(evil) (when completing) Insert separator DWIM
M-SPC	(emacs) (when completing) Insert separator DWIM
SPC	(when completing) Quit autocompletion
SPC	(when completing with separators) Self-insert

Exporting to the minibuffer

The entries shown in the completion popup can be exported to a completing-read minibuffer, giving access to all the manipulations that suite allows. Using Vertico for instance, one could use this to export with doom-package:embark via C-c C-l and get a buffer with all candidates.

Configuration

A few variables may be set to change behavior of this module:

var:completion-at-point-functions

This is not a module/package variable, but a builtin Emacs one. Even so, it's very important to how Corfu works, so we document it here. It contains a list of functions that are called in turn to generate completion candidates. The regular (non-lexical) value should contain few entries and they should generally be context aware, so as to predict what you need. Additional functions can be added as you get into more and more specific contexts. Also, there may be cases where you know beforehand the kind of candidate needed, and want to enable only that one. For this, the variable may be lexically bound to the correct value, or you may call the CAPF interactively if a single function is all you need.

var:corfu-auto-delay

Number of seconds till completion occurs automatically. Defaults to 0.1.

var:corfu-auto-prefix

Number of characters till auto-completion starts to happen. Defaults to 2.

var:corfu-on-exact-match

Configures behavior for exact matches.

var:corfu-preselect

Configures startup selection, choosing between the first candidate or the prompt.

var:corfu-preview-current

Configures current candidate preview.

var:+corfu-want-ret-to-confirm

Enables commiting with /yogsototh/doom-emacs/src/commit/15d7353946ad6523a6a41c5744f2cb2210bb4674/modules/completion/corfu/RET when the popup is visible. Default is t, may be set to 'minibuffer if you want to commit both the completion and the minibuffer when active. When nil, it is always passed-through.

var:+corfu-buffer-scanning-size-limit

Sets the maximum buffer size to be scanned by cape-dabbrev. Defaults to 1 MB. Set this if you are having performance problems using the CAPF.

var:+corfu-want-minibuffer-completion

Whether to enable Corfu in the minibuffer. See its documentation for additional tweaks.

Turning off auto-completion

To disable idle (as-you-type) completion, unset corfu-auto:

;;; in $DOOMDIR/config.el
(after! corfu
  (setq corfu-auto nil))

Adding CAPFs to a mode

To add other CAPFs on a mode-per-mode basis, put either of the following in your config.el:

(add-hook! some-mode (add-hook 'completion-at-point-functions #'some-capf depth t))
;; OR, but note the different call signature
(add-hook 'some-mode-hook (lambda () (add-hook 'completion-at-point-functions #'some-capf depth t)))

DEPTH above is an integer between -100, 100, and defaults to 0 if nil. Also see add-hook!'s documentation for additional ways to call it. add-hook only accepts the quoted arguments form above.

Adding CAPFs to a key

To add other CAPFs to keys, adapt the snippet below into your config.el:

(map! :map some-mode-map
      "C-x e" #'cape-emoji)

It's okay to add to the mode directly because completion-at-point works regardless of Corfu (the latter is an enhanced UI for the former). Just note not all CAPFs are interactive to be called this way, in which case you can use doom-package:cape's adapter to enable this.

Troubleshooting

Report an issue?

If you have performance issues with cape-dabbrev, the first thing I recommend doing is to look at the list of buffers Dabbrev is scanning:

(dabbrev--select-buffers) ; => (#<buffer README.org> #<buffer config.el<3>> #<buffer cape.el> ...)
(length (dabbrev--select-buffers)) ; => 37

… and modify dabbrev-ignored-buffer-regexps or dabbrev-ignored-buffer-modes accordingly.

If you see garbage completion candidates, you can use the following command to debug the issue:

;;;###autoload
(defun search-in-dabbrev-buffers (search-string)
  "Search for SEARCH-STRING in all buffers returned by `dabbrev--select-buffers'."
  (interactive "sSearch string: ")
  (let ((buffers (dabbrev--select-buffers)))
    (multi-occur buffers search-string)))

;; Example usage:
;; Why are these weird characters appearing in my completions?
(search-in-dabbrev-buffers "\342\200\231")

Frequently asked questions

This module has no FAQs yet. Ask one?

TODO Appendix

🔨 This module has no appendix yet. Write one?