all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Robert Pluim <rpluim@gmail.com>
Cc: 40216@debbugs.gnu.org
Subject: bug#40216: 28.0.50; Misinformation in isearch char-fold
Date: Fri, 27 Mar 2020 01:04:12 +0200	[thread overview]
Message-ID: <87ftdud8gj.fsf@mail.linkov.net> (raw)
In-Reply-To: <m21rpf86lt.fsf@gmail.com> (Robert Pluim's message of "Thu, 26 Mar 2020 16:43:10 +0100")

>     >> Do we need an option to char-fold-regexp that says 'only apply
>     >> char-folding to non-ascii characters'?
>
>     Eli> But this feature is not intended only to find variants of non-ASCII
>     Eli> characters when one searches for a non-ASCII, it is also intended to
>     Eli> find variants when searching for ASCII characters.  For example,
>     Eli> searching for a is supposed to find ä and à and á.  Or am I missing
>     Eli> something?
>
> Yes, thatʼs exactly right. But in the case where you have mainly
> characters where you donʼt want case-folding, it might make sense to
> restrict the folding to non-ascii as an optimisation. eg. Suppose my
> name were Røbert, with people frequently misspelling it as Robert, I
> might want isearch to just search for "R\\(?:ǿ\\|[øǿo]\\)bert"

I tried to find Røbert by typing Robert, but char-fold fails to find it.
A bug in char-fold?





  reply	other threads:[~2020-03-26 23:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24 23:00 bug#40216: 28.0.50; Misinformation in isearch char-fold Juri Linkov
2020-03-25  9:22 ` Robert Pluim
2020-03-25 20:29   ` Juri Linkov
2020-03-26  9:28     ` Robert Pluim
2020-03-26 14:25       ` Eli Zaretskii
2020-03-26 15:43         ` Robert Pluim
2020-03-26 23:04           ` Juri Linkov [this message]
2020-03-27  7:24             ` Eli Zaretskii
2020-03-27  8:30               ` Robert Pluim
2020-03-28 23:42                 ` Juri Linkov
2020-03-26 23:00       ` Juri Linkov

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=87ftdud8gj.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=40216@debbugs.gnu.org \
    --cc=rpluim@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 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.