From: Wanrong Lin <wrglin@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
39484@debbugs.gnu.org
Subject: bug#39484: 26.3; try-completion bug
Date: Tue, 27 Oct 2020 20:47:31 -0400 [thread overview]
Message-ID: <d8b68c2d-e6dd-0717-1cc7-c3e9c6581272@gmail.com> (raw)
In-Reply-To: <b7f02833-10fe-9b3f-3ab6-6f06aef489a2@gmail.com>
Sorry, I meant "abcd" as the answer for your example.
On 10/27/2020 8:44 PM, Wanrong Lin wrote:
> For this case, "abc" might be OK, unless you think there is another
> better answer. But in the example I gave, don't you think "Xyz" is
> obviously a better answer than "xyz"?
>
> The argument here is for some examples, the function does not return
> the best answer, and also, does not seem to be consistent to me (for
> those two examples I gave). There might be a reason behind this
> "compromise", or, it might be just an arbitrary decision as documented
> in the comments you gave. If it is the latter, can we improve on it? I
> think those are valid questions.
>
> Wanrong
>
> On 10/27/2020 5:21 PM, Andreas Schwab wrote:
>> So what should (try-completion "abc" '("Abcde" "aBcdf" "abCdg")) return?
>>
>> Andreas.
>>
>
next prev parent reply other threads:[~2020-10-28 0:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 15:44 bug#39484: 26.3; try-completion bug Wanrong Lin
2020-10-27 18:42 ` Lars Ingebrigtsen
2020-10-27 19:08 ` Andreas Schwab
2020-10-27 19:17 ` Lars Ingebrigtsen
2020-10-27 20:17 ` Wanrong Lin
2020-10-27 20:28 ` Andreas Schwab
2020-10-27 20:44 ` Wanrong Lin
2020-10-27 21:21 ` Andreas Schwab
2020-10-28 0:44 ` Wanrong Lin
2020-10-28 0:47 ` Wanrong Lin [this message]
2020-10-28 0:57 ` Wanrong Lin
2020-10-28 7:51 ` Andreas Schwab
2020-10-28 9:35 ` Lars Ingebrigtsen
2020-10-28 9:42 ` Andreas Schwab
2020-10-28 9:50 ` Lars Ingebrigtsen
2020-10-28 9:56 ` Andreas Schwab
2020-10-28 11:16 ` Lars Ingebrigtsen
2020-10-28 11:44 ` Andreas Schwab
2020-10-28 12:59 ` Wanrong Lin
2020-10-28 14:45 ` Stefan Monnier
2020-10-28 15:47 ` Wanrong Lin
2020-10-28 16:34 ` Stefan Monnier
2022-04-23 13:17 ` Lars Ingebrigtsen
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=d8b68c2d-e6dd-0717-1cc7-c3e9c6581272@gmail.com \
--to=wrglin@gmail.com \
--cc=39484@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.org \
/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).