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:00:18 +0200 [thread overview]
Message-ID: <87mu82d8n1.fsf@mail.linkov.net> (raw)
In-Reply-To: <m2imirea7c.fsf@gmail.com> (Robert Pluim's message of "Thu, 26 Mar 2020 10:28:55 +0100")
> Ah, I hadn't considered that use case. Do we need an option to
> char-fold-regexp that says 'only apply char-folding to non-ascii
> characters'? That would reduce the size of the regexp considerably.
Currently there are 2 covered use cases:
1. the default is to fold ascii to non-ascii characters;
2. non-nil char-fold-symmetric additionally folds
non-ascii to ascii characters.
It seems you are proposing a third use case:
3. symmetric-only that can be implemented with a new non-nil option
char-fold-symmetric-only that will fold only non-ascii characters
to ascii.
I have doubts how useful this will be.
The current default behavior is useful when the user types
ascii characters on the keyboard with ascii characters only.
The option char-fold-symmetric is useful to match pasted text
both ways ignoring all differences between ascii/non-ascii characters.
But for symmetric-only I can't imagine any useful use case.
For example, when you paste non-ascii characters into the search string,
and want to find corresponding ascii characters. But why wouldn't you
want to find the other way around: pasting ascii characters
to find non-ascii counterparts?
prev parent reply other threads:[~2020-03-26 23:00 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
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 [this message]
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=87mu82d8n1.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 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).