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: Sun, 13 Mar 2022 22:15:12 +0100 [thread overview]
Message-ID: <20220313211512.2kqyqcdpylxe2mgb@Ergus> (raw)
In-Reply-To: <SJ0PR10MB5488322127622168E9B8A751F30E9@SJ0PR10MB5488.namprd10.prod.outlook.com>
On Sun, Mar 13, 2022 at 08:48:22PM +0000, Drew Adams wrote:
>> In case of no completions it will be formatted to: "0 possible
>> completions".
>
>Why? Why wouldn't *Completions* just be
>removed? And "[No match]" is already echoed.
>
In the original code there is a message to print when there are no
completions, that's where the original question came from. Actually the
new code is simpler.
>Sounds like things are getting more, not less,
>complicated for users (maybe overengineering?).
>
For the user everything is pretty much the same.
>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.
>
next prev parent reply other threads:[~2022-03-13 21:15 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220313211512.2kqyqcdpylxe2mgb@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.