dotfiles-misc/protesilaos.dotfiles
1
0
Fork 0
mirror of https://github.com/protesilaos/dotfiles.git synced 2026-09-10 07:16:20 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

emacs: configure cape to be active unless company is enabled

Browse source
This commit is contained in:
Protesilaos 2026-08-30 15:00:20 +03:00
parent 971029cda0
commit 43d549d985
No known key found for this signature in database
GPG key ID: 99BD6459CD5CA3EA
2 changed files with 14 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
emacs/.emacs.d/prot-emacs-modules/prot-emacs-completion.el
View file

@ -280,7 +280,7 @@ excerpt: \"Just read the poem. No further comment.\"
(corfu-history-mode 1)
(add-to-list 'savehist-additional-variables 'corfu-history))))
(when (eq prot-emacs-completion-in-buffer 'corfu)
(unless (eq prot-emacs-completion-in-buffer 'company)
(prot-emacs-configure
(prot-emacs-install cape)

18
emacs/.emacs.d/prot-emacs.org
View file

@ -4831,13 +4831,21 @@ specific to a given buffer will take precedence over the corresponding
global value. Being mindful of these nuances does, nevertheless,
empower us to do things exactly how we like them.
Finally, Cape is not tied to ~corfu~ though I only use them in tandem
([[#h:804b858f-7913-47ef-aaf4-8eef5b59ecb4][The =prot-emacs-completion.el= settings for in-buffer completion popup (~corfu~)]]).
The reason is that ~company~ implements its own backends, which are
just as good in my experience ([[#h:6d3e2d44-9b1e-4092-8287-5062e4f29da4][The =prot-emacs-completion.el= about the in-buffer completion popup (~company~)]]).
Finally, Cape is not tied to ~corfu~: it can be used with the built-in
=*Completions*= buffer or the ~completion-preview-mode~ just as well.
- [[#h:804b858f-7913-47ef-aaf4-8eef5b59ecb4][The =prot-emacs-completion.el= settings for in-buffer completion popup (~corfu~)]].
- [[#h:bb7959b3-d8e6-4163-8e32-bec2b96b7dde][The =prot-emacs-completion.el= for in-buffer completion hints (~completion-preview-mode~)]].
- [[#h:de61a607-0bdf-462b-94cd-c0898319590e][The =prot-emacs-completion.el= generic minibuffer UI settings]].
Though we normally do not need ~cape~ together with ~company~. The
reason is that ~company~ implements its own backends, which are just
as good in my experience ([[#h:6d3e2d44-9b1e-4092-8287-5062e4f29da4][The =prot-emacs-completion.el= about the in-buffer completion popup (~company~)]]).
Technically, it is possible to use Company backends via Cape, though I
have not found a comppelling reason to do this.
#+begin_src emacs-lisp :tangle "prot-emacs-modules/prot-emacs-completion.el"
(when (eq prot-emacs-completion-in-buffer 'corfu)
(unless (eq prot-emacs-completion-in-buffer 'company)
(prot-emacs-configure
(prot-emacs-install cape)