From: Ergus <spacibba@aol.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Juri Linkov <juri@linkov.net>, Po Lu <luangruo@yahoo.com>,
Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [External] : Re: Question about completion behavior
Date: Mon, 14 Mar 2022 00:38:00 +0100 [thread overview]
Message-ID: <20220313233800.44vfuwjje6wgsdm2@Ergus> (raw)
In-Reply-To: <SJ0PR10MB5488FC28453A05DB1FE7EC25F30E9@SJ0PR10MB5488.namprd10.prod.outlook.com>
On Sun, Mar 13, 2022 at 11:14:56PM +0000, Drew Adams wrote:
Hi Drew:
Man, please relax...
>
>Doesn't sound like it - not regarding what I
>asked about, at least.
>
>I have nothing against keeping *Completions*
>showing and updating it as a user changes the
>pattern to match (and either explicitly asks
>for a rematch or has elected to get automatic
>rematching).
>
>In fact, I invented such behavior for Emacs
>(a couple decades ago).
>
>But why would we not _remove_ *Completions*
>when there are no matches?
>
>We tell users in the echo area that there are
>no matches. Why also show an empty buffer,
>for nonexistent completions, with a redundant
>message there saying there are none?
>
>(That's IBM's "This page intentionally left
>blank." But at least there was a reason for
>that notice.)
>
>Maybe "the new code is simpler". It sounds
>like the new user experience is less simple
>- and maybe a step backward.
>
>I understand your feature would be optional.
>It sounds like it has room for improvement.
>
The user experience is exactly the same than before. Just that now
there is an option to change, suppress or/and get a counter with the
total number of completions where there was before just a bit
superfluous hard-coded message: "Possible completions are:"
That's it. Everything else is exactly the same. As usual, I am not doing
rocket engineering here; I am just adding something simple and obvious
that nobody wanted to give any attention before; in spite of many more
experienced lispers like you could implement this in 30 minutes two
decades ago ;p.
>> > Why would we ever say "0 possible completions"?
>> >
>> > Why bother with "possible"? We never show
>> > IMpossible completions, do we?
>> >
>> > When there are no matches we just tell users
>> > there's no match. Always have. Simple.
>
>And your answer is?
Because the original message was: "Possible completions are:" and it has
been there since ever without hearing your complains about that the
completions are not IMpossible.
I don't care anything about one word at all and if the user doesn't like
the word or you want to put there "Drews completions are:", at least now
you have an option to customize it as you prefer...
Best,
Ergus
next prev parent reply other threads:[~2022-03-13 23:38 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220313233800.44vfuwjje6wgsdm2@Ergus \
--to=spacibba@aol.com \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--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 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.