From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Po Lu <luangruo@yahoo.com>, emacs-devel@gnu.org
Subject: Re: Awful completion buffer behaviour
Date: Wed, 22 Dec 2021 14:55:17 +0000 [thread overview]
Message-ID: <87ilvgu1t6.fsf@posteo.net> (raw)
In-Reply-To: <83bl18yc2e.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 22 Dec 2021 16:00:09 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Po Lu <luangruo@yahoo.com>
>> Cc: emacs-devel@gnu.org
>> Date: Wed, 22 Dec 2021 20:56:00 +0800
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > I agree that this new behavior is an unpleasant surprise for me.
>> >
>> > I'm not sure I understand the purpose of the month-long experiment
>> > with turning this on by default. Is it to decide whether it will stay
>> > on in Emacs 29? If so, the experiment can be terminated now: we will
>> > not make this the default, certainly not in Emacs 29, and maybe not
>> > even in Emacs 30. It is too radical departure of age-old Emacs
>> > behavior in the default completion commands.
>>
>> Thanks, will you mind if I install a change that documents the option
>> in the NEWS entry and changes its default value to nil now?
>
> I'd like to hear from Juri and Philip first.
The idea was to gather feedback, and this thread is one form of
feedback. If the feature is as intrusive as described here (for which I
would like to apologise), then it seems like it should be disabled.
--
Philip Kaludercic
next prev parent reply other threads:[~2021-12-22 14:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <878rwdtjum.fsf.ref@yahoo.com>
2021-12-22 3:10 ` Awful completion buffer behaviour Po Lu
2021-12-22 8:54 ` Juri Linkov
2021-12-22 9:25 ` Po Lu
2021-12-22 17:56 ` Juri Linkov
2021-12-22 10:39 ` Po Lu
2021-12-22 12:53 ` Eli Zaretskii
2021-12-22 12:56 ` Po Lu
2021-12-22 13:35 ` Po Lu
2021-12-22 14:03 ` Eli Zaretskii
2021-12-22 14:00 ` Eli Zaretskii
2021-12-22 14:55 ` Philip Kaludercic [this message]
2021-12-22 17:40 ` Juri Linkov
2021-12-23 9:06 ` Robert Pluim
2021-12-23 17:27 ` Juri Linkov
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=87ilvgu1t6.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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 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).