From: Philip Kaludercic <philipk@posteo.net>
To: Juri Linkov <juri@linkov.net>
Cc: emacs-devel@gnu.org
Subject: Re: master f6967d2 1/3: Allow for the completion buffer to be automatically selected
Date: Fri, 03 Jun 2022 08:57:25 +0000 [thread overview]
Message-ID: <87sfom3z0q.fsf@posteo.net> (raw)
In-Reply-To: <86k0a1vb4n.fsf@mail.linkov.net> (Juri Linkov's message of "Tue, 31 May 2022 20:56:56 +0300")
Juri Linkov <juri@linkov.net> writes:
>> The idea is that completion-auto-select and completion-wrap-movement
>> provide is a method to reduce all completion operations to a single
>> key (tab), without having to change modifiers.
>
> Every time I customize completion options, first I change
> completion-auto-help and completion-auto-select, then spend
> time trying to find the third related variable under the same prefix.
> Does this suggest it would be better to share the same prefix,
> i.e. to name the third variable completion-auto-wrap?
I think that would make sense, or at least I would never object to
consistency.
prev parent reply other threads:[~2022-06-03 8:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1sfulwmqp.fsf.ref@yahoo.es>
2021-12-21 23:40 ` master f6967d2 1/3: Allow for the completion buffer to be automatically selected Daniel Martín
2021-12-22 8:58 ` Juri Linkov
2021-12-22 9:27 ` Po Lu
2021-12-22 11:07 ` Lars Ingebrigtsen
2021-12-22 17:59 ` Juri Linkov
2021-12-22 9:48 ` tomas
2021-12-22 13:48 ` Philip Kaludercic
2021-12-22 17:45 ` Juri Linkov
2021-12-22 20:02 ` Philip Kaludercic
2021-12-23 6:34 ` Eli Zaretskii
2021-12-23 17:23 ` Juri Linkov
2021-12-23 18:44 ` [External] : " Drew Adams
2021-12-22 19:39 ` Theodor Thornhill
2021-12-22 21:18 ` Daniel Martín
2021-12-22 21:30 ` Theodor Thornhill
2021-12-22 23:04 ` Philip Kaludercic
2022-05-31 17:56 ` Juri Linkov
2022-06-03 8:57 ` Philip Kaludercic [this message]
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=87sfom3z0q.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
/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.