From: Ergus <spacibba@aol.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Po Lu <luangruo@yahoo.com>, Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Question about completion behavior
Date: Wed, 9 Mar 2022 18:41:57 +0100 [thread overview]
Message-ID: <20220309174157.ckvbocjmxzkeopdy@Ergus> (raw)
In-Reply-To: <jwvk0d3uj98.fsf-monnier+emacs@gnu.org>
On Wed, Mar 09, 2022 at 12:32:14PM -0500, Stefan Monnier wrote:
>Po Lu [2022-03-09 21:46:06] wrote:
>> Eli Zaretskii <eliz@gnu.org> writes:
>>> But yes, I think this behavior you propose _must_ be optional, most
>>> probably opt-in for starters. Not everyone will want it.
>> I agree completely. I'm sure many people have developed a lot of muscle
>> memory regarding completion, and even tiny changes will probably be a
>> nusiance to them.
Hi Stefan:
>
>Then again, it's only by enabling it by default that we'll get a clear
>picture of which changes are annoyances are which aren't.
>
I just sent a patch here with new custom values for completion-auto-help
as Eli suggested.
>So I'd start by changing the default on `master` and after a month or
>so, collect feedback to decide how to go about adding it: either by just
>changing the behavior willy-nilly, or introduce it but add an option to
>revert to the old behavior, or leave the default unchanged but add an
>option to get the new behavior, ...
>
I agree with this approach by 110%. I think it is sensible and we can
try to put the 'visual value as default without excessive complains. As
it is consistent enough but also improves a bit the behavior based on
your initial comment without affecting too much the previous behavior.
>
> Stefan
>
next prev parent reply other threads:[~2022-03-09 17:41 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220309001013.gxyh2uasbuxiz6ww.ref@Ergus>
2022-03-09 0:10 ` Question about completion behavior Ergus
2022-03-09 0:22 ` Stefan Monnier
2022-03-09 1:46 ` Ergus
2022-03-09 3:05 ` Stefan Monnier
2022-03-09 3:37 ` Eli Zaretskii
2022-03-09 10:11 ` Ergus
2022-03-09 11:46 ` Ergus
2022-03-09 13:16 ` Eli Zaretskii
2022-03-09 13:46 ` Po Lu
2022-03-09 17:32 ` Stefan Monnier
2022-03-09 17:41 ` Ergus [this message]
2022-03-10 0:42 ` Po Lu
2022-03-10 10:21 ` Ergus
2022-03-10 11:15 ` Po Lu
2022-03-10 14:03 ` Ergus
2022-03-10 18:50 ` Juri Linkov
2022-03-10 22:35 ` Ergus
2022-03-12 18:31 ` Juri Linkov
2022-03-13 14:58 ` Ergus
2022-03-12 0:17 ` Ergus
2022-03-12 18:34 ` Juri Linkov
2022-03-13 11:21 ` Ergus
2022-03-13 17:44 ` Juri Linkov
2022-03-13 18:50 ` Ergus
2022-03-13 18:57 ` Eli Zaretskii
2022-03-13 19:49 ` Ergus
2022-03-13 20:48 ` [External] : " Drew Adams
2022-03-13 21:15 ` Ergus
2022-03-13 23:14 ` Drew Adams
2022-03-13 23:38 ` Ergus
2022-03-14 2:23 ` Drew Adams
2022-03-12 20:25 ` Drew Adams
2022-03-09 14:30 ` Ergus
2022-03-09 16:14 ` [PATCH] " Ergus
2022-03-09 16:56 ` Eli Zaretskii
2022-03-09 13:10 ` Eli Zaretskii
2022-03-09 14:22 ` Ergus
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220309174157.ckvbocjmxzkeopdy@Ergus \
--to=spacibba@aol.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).