unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: greselin.andrea@gmail.com, 52394@debbugs.gnu.org
Subject: bug#52394: 27.2; Isearch with char folding enabled doesn’t match equivalent strings
Date: Sun, 12 Dec 2021 20:43:53 +0200	[thread overview]
Message-ID: <834k7doe8m.fsf@gnu.org> (raw)
In-Reply-To: <861r2hllql.fsf@mail.linkov.net> (message from Juri Linkov on Sun, 12 Dec 2021 20:30:10 +0200)

> From: Juri Linkov <juri@linkov.net>
> Cc: greselin.andrea@gmail.com,  52394@debbugs.gnu.org
> Date: Sun, 12 Dec 2021 20:30:10 +0200
> 
> >> > Doesn't this change the default behavior?
> >> 
> >> No, no change in the default behavior.
> >
> > Then I guess the doc string of the defcustom is confusing?  Can you
> > make it more clear wrt what each value means in practice?
> 
> Here is the doc string.  How do you propose to make it more clear?
> 
>     "Non-nil means to override all default folding characters.
>   When nil, the equivalence table is populated with the default set
>   of equivalent chars, and you can remove unneeded characters using
>   `char-fold-exclude', and add own characters using `char-fold-include'.
>   But when this variable is customized to non-nil, you start with
>   an empty table where you can add only own characters
>   using `char-fold-include'."

My reading of this is that the feature by default will not work at all:
since the default value is not nil, the doc string says that I "start
with an empty table", so no folding will happen.  Is that what you
meant?  And if so, how isn't this a change in behavior?  In Emacs 27
the folding works by default and finds equivalent characters without
any user intervention.

What am I missing?





  reply	other threads:[~2021-12-12 18:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09 20:41 bug#52394: 27.2; Isearch with char folding enabled doesn’t match equivalent strings Andrea Greselin
2021-12-10  2:00 ` Michael Heerdegen
2021-12-10  7:51 ` Juri Linkov
2021-12-10 11:00   ` Andrea Greselin
2021-12-11 19:46     ` Juri Linkov
2021-12-11 20:13       ` Andrea Greselin
2021-12-11 20:34         ` Juri Linkov
2021-12-11 21:14           ` Andrea Greselin
2021-12-12  8:37             ` Juri Linkov
2021-12-12  9:31               ` Andrea Greselin
2021-12-12 17:19                 ` Juri Linkov
2021-12-12 17:53                   ` Eli Zaretskii
2021-12-12 18:06                     ` Juri Linkov
2021-12-12 18:25                       ` Eli Zaretskii
2021-12-12 18:30                         ` Juri Linkov
2021-12-12 18:43                           ` Eli Zaretskii [this message]
2021-12-12 18:54                             ` Juri Linkov
2021-12-12 18:59                               ` Eli Zaretskii
2021-12-12 19:12                                 ` 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

  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=834k7doe8m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=52394@debbugs.gnu.org \
    --cc=greselin.andrea@gmail.com \
    --cc=juri@linkov.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 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).