From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-28 a866674b2a: Fix inaccuracies in "lax search" documentation
Date: Tue, 26 Jul 2022 16:16:35 +0300 [thread overview]
Message-ID: <83fsioc8uk.fsf@gnu.org> (raw)
In-Reply-To: <8735eo829i.fsf@gmail.com> (message from Robert Pluim on Tue, 26 Jul 2022 14:52:25 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Tue, 26 Jul 2022 14:52:25 +0200
>
> >>>>> On Mon, 25 Jul 2022 16:43:59 +0300, Eli Zaretskii <eliz@gnu.org> said:
>
> >> From: Robert Pluim <rpluim@gmail.com>
> >> Cc: Eli Zaretskii <eliz@gnu.org>
> >> Gmane-Reply-To-List: yes
> >> Date: Mon, 25 Jul 2022 15:01:38 +0200
> >>
> >> Should we make `char-fold-to-regexp' into a command and refer to it
> >> from here? Or add something like `char-fold-show-equivalences'?
>
> Eli> I'm not sure I understand what you have in mind, but if the intent is
> Eli> to allow easier customization of char-fold.el, I'm for it.
>
> I didnʼt pick up on this earlier. What do you mean by "easier
> customization of char-fold.el"? I thought the various include/exclude
> vars were all customizable already?
Yes, but the values are not very friendly for interactive
customizations, IMNSHO.
Anyway, if you didn't mean to do anything about that, I'm okay with
the status quo.
next prev parent reply other threads:[~2022-07-26 13:16 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165875050243.3275.8867100069985547389@vcs2.savannah.gnu.org>
[not found] ` <20220725120142.D1283C0F203@vcs2.savannah.gnu.org>
2022-07-25 13:01 ` emacs-28 a866674b2a: Fix inaccuracies in "lax search" documentation Robert Pluim
2022-07-25 13:43 ` Eli Zaretskii
2022-07-25 14:48 ` Robert Pluim
2022-07-25 16:02 ` Eli Zaretskii
2022-07-26 12:52 ` Robert Pluim
2022-07-26 13:16 ` Eli Zaretskii [this message]
2022-07-26 14:23 ` Robert Pluim
2022-07-26 16:06 ` Eli Zaretskii
2022-07-26 16:54 ` Robert Pluim
2022-07-26 17:15 ` Eli Zaretskii
2022-07-27 7:54 ` Robert Pluim
2022-07-27 11:32 ` Eli Zaretskii
2022-07-25 17:52 ` Juri Linkov
2022-07-25 18:15 ` Eli Zaretskii
2022-07-25 18:42 ` Juri Linkov
2022-07-25 19:49 ` Juri Linkov
2022-07-26 7:59 ` Robert Pluim
2022-07-26 12:16 ` Eli Zaretskii
2022-07-27 7:46 ` Juri Linkov
2022-07-27 8:13 ` Robert Pluim
2022-07-27 11:32 ` Eli Zaretskii
2022-07-27 18:54 ` Juri Linkov
2022-07-27 19:23 ` Eli Zaretskii
2022-07-27 19:55 ` Juri Linkov
2022-07-28 5:40 ` Eli Zaretskii
2022-07-28 6:07 ` Eli Zaretskii
2022-07-28 7:13 ` Juri Linkov
2022-07-28 7:56 ` Eli Zaretskii
2022-07-28 7:10 ` Juri Linkov
2022-07-28 7:55 ` Eli Zaretskii
2022-07-28 19:40 ` Juri Linkov
2022-08-30 7:29 ` Juri Linkov
2022-08-31 8:49 ` Robert Pluim
2022-08-31 16:09 ` Juri Linkov
2022-08-31 16:36 ` Robert Pluim
2022-08-31 16:40 ` Eli Zaretskii
2022-08-31 16:56 ` Robert Pluim
2022-08-31 17:13 ` Juri Linkov
2022-08-31 17:22 ` Eli Zaretskii
2022-08-31 17:26 ` Robert Pluim
2022-08-31 17:29 ` [External] : " Drew Adams
2022-08-31 18:04 ` Juri Linkov
2022-08-31 20:14 ` Stefan Monnier
2022-09-01 7:22 ` Juri Linkov
2022-09-01 8:14 ` Robert Pluim
2022-09-01 11:34 ` Eli Zaretskii
2022-09-01 12:23 ` Robert Pluim
2022-09-01 13:00 ` Stefan Monnier
2022-09-01 13:07 ` Robert Pluim
2022-09-01 15:28 ` Robert Pluim
2022-09-01 15:30 ` Eli Zaretskii
2022-09-01 15:58 ` Robert Pluim
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=83fsioc8uk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@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).