From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 11339@debbugs.gnu.org, stephen.berman@gmx.net, stefan@marxist.se
Subject: bug#11339: 24.1.50; read-{buffer,file-name}-completion-ignore-case fails on non-ascii
Date: Sat, 09 Nov 2019 13:24:06 -0500 [thread overview]
Message-ID: <jwvtv7cuczk.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83eeyh9zjn.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 09 Nov 2019 11:20:12 +0200")
> What about the below? It passes all the tests, and also fixes the
> original use case.
Sounds good. I have the impression that I was the original author of
that "early exit" optimization (or at least some of it), but my brain
must be decaying because I have a hard time understanding the code.
I also wonder if it's really worth the effort (of the optimization,
I mean).
Stefan
next prev parent reply other threads:[~2019-11-09 18:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 15:37 bug#11339: 24.1.50; read-{buffer,file-name}-completion-ignore-case fails on non-ascii Stephen Berman
2013-07-08 22:08 ` Stephen Berman
2019-11-01 19:57 ` Stefan Kangas
2019-11-01 20:20 ` Eli Zaretskii
2019-11-01 22:37 ` Stephen Berman
2019-11-02 7:11 ` Eli Zaretskii
2019-11-02 15:09 ` Stephen Berman
2019-11-03 16:16 ` Eli Zaretskii
2019-11-04 13:39 ` Stephen Berman
2019-11-04 16:21 ` Eli Zaretskii
2019-11-04 16:22 ` Stephen Berman
2019-11-04 17:12 ` Eli Zaretskii
2019-11-04 18:02 ` Stephen Berman
2019-11-06 16:58 ` Eli Zaretskii
2019-11-07 14:34 ` Stephen Berman
2019-11-07 14:49 ` Eli Zaretskii
2019-11-07 16:01 ` Stefan Monnier
2019-11-07 16:08 ` Eli Zaretskii
2019-11-07 16:27 ` Stefan Monnier
2019-11-07 18:12 ` Eli Zaretskii
2019-11-08 22:36 ` Stefan Monnier
2019-11-09 9:20 ` Eli Zaretskii
2019-11-09 17:56 ` Stephen Berman
2019-11-09 18:24 ` Stefan Monnier [this message]
2019-11-09 19:57 ` Eli Zaretskii
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=jwvtv7cuczk.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=11339@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefan@marxist.se \
--cc=stephen.berman@gmx.net \
/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.