unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Wanrong Lin <wrglin@gmail.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	39484@debbugs.gnu.org
Subject: bug#39484: 26.3; try-completion bug
Date: Wed, 28 Oct 2020 10:42:51 +0100	[thread overview]
Message-ID: <87zh461yas.fsf@igel.home> (raw)
In-Reply-To: <87tuuevgl2.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 28 Oct 2020 10:35:05 +0100")

On Okt 28 2020, Lars Ingebrigtsen wrote:

> Andreas Schwab <schwab@linux-m68k.org> writes:
>
>> On Okt 27 2020, Wanrong Lin wrote:
>>
>>> The answer is not bad, matching at least one of the candidates. That makes
>>> the answer to my original example even more odd:
>>> (let ((completion-ignore-case t))
>>>        (try-completion "xyz" '("XyzD" "XyzAbc"))
>>>        )
>>> ==> "xyz"
>>
>> That also matches one of the candidates (since case doesn't matter).
>
> It does, but it's weird.  I mean, this pair of return values don't make
> sense on any level:
>
> (let ((completion-ignore-case t))
>   (try-completion "xyz" '("XyzaD" "XyZabc")))
> => "Xyza"
>
> (let ((completion-ignore-case t))
>   (try-completion "xyz" '("XyZbD" "XyZabc")))
> => "xyz"  

It makes a whole lot sense.  If the candidate is not modified, it
should not receive any case changes either.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."





  reply	other threads:[~2020-10-28  9:42 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
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 [this message]
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=87zh461yas.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=39484@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=wrglin@gmail.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).