From d8740fe4cb9a3988669efd7f86868c9b417b0d72 Mon Sep 17 00:00:00 2001 From: Eshel Yaron Date: Fri, 17 Nov 2023 19:56:54 +0100 Subject: [PATCH] Update Completion Preview post --- source/posts/2023-11-17-completion-preview-in-emacs.org | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/posts/2023-11-17-completion-preview-in-emacs.org b/source/posts/2023-11-17-completion-preview-in-emacs.org index e32ffad..92bafbe 100644 --- a/source/posts/2023-11-17-completion-preview-in-emacs.org +++ b/source/posts/2023-11-17-completion-preview-in-emacs.org @@ -60,10 +60,10 @@ in-buffer completions, no extra configuration needed. You can think of Completion Preview as another, second, "frontend" for ~completion-at-point-functions~. I explicitly say it's a second frontend, because Completion Preview does not replace your regular -completion selection UI, be it [[https://github.com/minad/corfu][~corfu~]] and its kind or the good old -=*Completions*= buffer. The preview and the selection UI are two -complementary features, so you can use Completion Preview with any -completion UI. +completion selection UI, be it [[https://github.com/minad/corfu][~corfu~]] and its kind, +~icomplete-in-buffer~, or the good old =*Completions*= buffer. The +preview and the selection UI are two complementary features, so you +can use Completion Preview with any completion selection UI. The second important question is "when exactly is the preview shown?" The answer is that it /may/ be shown after each command. My initial -- 2.39.2