From: Dmitry Gutov <dmitry@gutov.dev>
To: Eshel Yaron <me@eshelyaron.com>
Cc: "Alexander Adolf" <alexander.adolf@condition-alpha.com>,
"João Távora" <joaotavora@gmail.com>,
"Juri Linkov" <juri@linkov.net>, "Eli Zaretskii" <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Inline completion preview
Date: Wed, 1 Nov 2023 14:24:23 +0200 [thread overview]
Message-ID: <38d20b8d-af34-757c-b990-19b4424eeeb8@gutov.dev> (raw)
In-Reply-To: <afe090d9-e8c7-792a-77ba-4ce016d70346@gutov.dev>
Sorry,
On 01/11/2023 14:14, Dmitry Gutov wrote:
> On 01/11/2023 10:30, Eshel Yaron wrote:
>> Either way, `C-M-i` seems like a natural choice since inserting the
>> previewed completion is strongly related to `completion-at-point`, so
>> the idea is that this key combination does something similar
>> (completion) whether the preview is visible or not. WDYT?
>
> It removes certain power from the user, namely, being able to press
> C-M-i to see all available completions, not just the previewed one.
>
> I think I'd simply use RET as the key. Since the preview only appears
> after the user had pressed C-M-i already, this should conflict with the
> regular usage of RET.
^ shouldn't
next prev parent reply other threads:[~2023-11-01 12:24 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 18:11 Inline completion preview Eshel Yaron
2023-10-26 18:38 ` Eli Zaretskii
2023-10-26 19:39 ` Eshel Yaron
2023-10-27 5:52 ` Eli Zaretskii
2023-10-27 15:43 ` Eshel Yaron
2023-10-27 17:12 ` Eli Zaretskii
2023-10-27 18:13 ` Eshel Yaron
2023-10-27 20:25 ` chad
2023-10-28 16:47 ` Juri Linkov
2023-10-28 19:01 ` Eshel Yaron
2023-10-29 16:24 ` Alexander Adolf
2023-10-29 23:29 ` João Távora
2023-10-30 9:25 ` Juergen Fenn
2023-10-30 9:36 ` João Távora
2023-10-30 11:04 ` Dmitry Gutov
2023-10-30 12:42 ` Alexander Adolf
2023-10-30 13:01 ` João Távora
2023-10-30 17:32 ` Alexander Adolf
2023-10-30 17:52 ` João Távora
2023-10-30 13:20 ` Dmitry Gutov
2023-10-30 17:43 ` Alexander Adolf
2023-10-30 22:49 ` Dmitry Gutov
2023-10-31 6:50 ` Eshel Yaron
2023-10-31 17:31 ` Alexander Adolf
2023-10-31 17:43 ` Eshel Yaron
2023-10-31 23:29 ` Dmitry Gutov
2023-11-01 8:30 ` Eshel Yaron
2023-11-01 10:11 ` João Távora
2023-11-01 10:44 ` Eshel Yaron
2023-11-01 11:07 ` João Távora
2023-11-01 12:17 ` Eshel Yaron
2023-11-01 12:23 ` Dmitry Gutov
2023-11-01 14:07 ` Juergen Fenn
2023-11-01 19:57 ` Dmitry Gutov
2023-11-01 12:08 ` Dmitry Gutov
2023-11-01 12:14 ` Dmitry Gutov
2023-11-01 12:24 ` Dmitry Gutov [this message]
2023-11-01 12:29 ` Eshel Yaron
2023-11-01 12:32 ` Dmitry Gutov
2023-11-01 12:34 ` Eli Zaretskii
2023-11-01 12:36 ` Dmitry Gutov
2023-11-01 13:28 ` Po Lu
2023-11-01 19:49 ` Dmitry Gutov
2023-10-27 8:58 ` Ihor Radchenko
2023-10-27 15:53 ` Eshel Yaron
2023-10-27 11:49 ` João Távora
2023-10-27 11:52 ` João Távora
2023-10-27 12:18 ` Eli Zaretskii
2023-10-27 12:55 ` João Távora
2023-10-27 12:58 ` Eli Zaretskii
2023-10-27 13:05 ` Dmitry Gutov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38d20b8d-af34-757c-b990-19b4424eeeb8@gutov.dev \
--to=dmitry@gutov.dev \
--cc=alexander.adolf@condition-alpha.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=juri@linkov.net \
--cc=me@eshelyaron.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.