From: Mike Kupfer <m.kupfer@acm.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Questions about isearch
Date: Fri, 27 Nov 2015 17:36:08 -0800 [thread overview]
Message-ID: <3719.1448674568@allegro.localdomain> (raw)
In-Reply-To: Your message of "Fri, 27 Nov 2015 22:06:54 +0200." <83poyvqk9t.fsf@gnu.org>
Eli Zaretskii wrote:
> > From: Mike Kupfer <m.kupfer@acm.org>
> > cc: emacs-devel@gnu.org
> > Date: Fri, 27 Nov 2015 11:50:18 -0800
> >
> > Assuming that there won't be any major changes for 25.1 in this area, I
> > think it would be helpful for the "Lax Search" Info node to say
> > something about replace-character-fold, particularly since that node
> > mentions the relationship between case-fold-search and replace commands.
> > And maybe replace-character-fold should be listed in the "Search
> > Customizations" node?
>
> There's a companion node "Replacement and Lax Matches", which
> describes this variable.
Okay, so can a cross-reference to "Replacement and Lax Matches" be added
to the "Lax Search" node? I mean, I did what you suggested in an
earlier reply to someone else: I went straight to the "Lax Search" node.
I didn't see anything in there to give me a clue about
replace-character-fold. I did see the cross-reference to "Replace", but
that was in the context of case-fold-search, which, unlike character
folding, does apply to replace commands. With the current "Lax Search"
text, there's just not enough of a hint to the reader that additional
important information is available.
Also, will the help strings for the search and the replace functions be
updated to mention the relevant character folding variables? They
already mention case-fold-search. (And I'd be less concerned about the
"Lax Search" text if the help string gave me the right clue.)
thanks,
mike
next prev parent reply other threads:[~2015-11-28 1:36 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 18:41 Questions about isearch Eli Zaretskii
2015-11-25 19:20 ` Rasmus
2015-11-25 20:02 ` Steinar Bang
2015-11-26 14:46 ` Richard Stallman
2015-11-26 16:22 ` Eli Zaretskii
2015-11-26 20:46 ` Per Starbäck
2015-11-26 21:02 ` Eli Zaretskii
2015-11-26 21:35 ` Marcin Borkowski
2015-11-27 7:43 ` Eli Zaretskii
2015-11-27 6:38 ` Richard Stallman
2015-11-27 8:53 ` Eli Zaretskii
2015-11-27 16:21 ` raman
2015-11-26 23:18 ` Rasmus
2015-11-27 7:46 ` Eli Zaretskii
2015-11-27 6:37 ` Richard Stallman
2015-11-27 8:39 ` Eli Zaretskii
2015-11-25 20:10 ` Eli Zaretskii
2015-11-25 20:41 ` Mike Kupfer
2015-11-25 20:56 ` Eli Zaretskii
2015-11-25 20:14 ` Artur Malabarba
2015-11-25 20:30 ` Marcin Borkowski
2015-11-25 20:38 ` Eli Zaretskii
2015-11-25 21:58 ` Artur Malabarba
2015-11-25 23:04 ` Mike Kupfer
2015-11-26 3:40 ` Eli Zaretskii
2015-11-27 19:50 ` Mike Kupfer
2015-11-27 20:06 ` Eli Zaretskii
2015-11-27 23:57 ` Artur Malabarba
2015-11-28 1:36 ` Mike Kupfer [this message]
2015-11-28 9:28 ` Eli Zaretskii
2015-11-26 13:28 ` Steinar Bang
2015-11-25 20:36 ` Eli Zaretskii
2015-11-25 21:49 ` Artur Malabarba
2015-11-26 3:34 ` Eli Zaretskii
2015-11-27 12:03 ` Artur Malabarba
2015-11-27 14:36 ` Eli Zaretskii
2015-11-27 16:50 ` Per Starbäck
2015-11-27 18:10 ` Artur Malabarba
2015-11-27 18:42 ` Per Starbäck
2015-11-27 21:33 ` raman
2016-02-28 0:27 ` Mathias Dahl
2016-02-28 15:58 ` Eli Zaretskii
2016-02-28 17:52 ` Mathias Dahl
2016-02-28 18:02 ` Eli Zaretskii
2016-02-29 13:32 ` Richard Stallman
2016-02-29 16:04 ` Eli Zaretskii
2016-03-01 16:52 ` Richard Stallman
2015-11-27 16:55 ` Artur Malabarba
2015-11-27 17:52 ` Eli Zaretskii
2015-11-27 21:18 ` Stephen Berman
2015-11-28 0:04 ` Artur Malabarba
2015-11-28 7:49 ` Eli Zaretskii
2015-11-28 16:14 ` Stephen Berman
2015-11-28 5:36 ` Richard Stallman
2015-11-28 8:33 ` Eli Zaretskii
2015-11-28 8:40 ` Marcin Borkowski
2015-11-28 9:46 ` Eli Zaretskii
2015-11-28 10:23 ` Artur Malabarba
2015-11-28 11:14 ` Eli Zaretskii
2015-11-28 14:41 ` Eli Zaretskii
2015-11-28 15:41 ` Artur Malabarba
2015-11-28 16:29 ` Artur Malabarba
2015-11-28 17:27 ` Eli Zaretskii
2015-11-28 17:44 ` Eli Zaretskii
2015-11-28 18:31 ` Artur Malabarba
2015-11-28 18:57 ` Eli Zaretskii
2015-11-28 20:00 ` Artur Malabarba
2015-11-28 20:08 ` Artur Malabarba
2015-11-28 20:47 ` Eli Zaretskii
2015-11-28 16:48 ` character folding future [was: Questions about isearch] Drew Adams
2015-11-28 18:34 ` Artur Malabarba
2015-12-01 11:34 ` Artur Malabarba
2015-12-01 15:48 ` Drew Adams
2015-12-03 23:54 ` Artur Malabarba
2015-11-29 6:03 ` Questions about isearch Richard Stallman
2015-11-29 15:48 ` Eli Zaretskii
2015-11-29 9:39 ` Andreas Röhler
2015-11-29 15:52 ` Eli Zaretskii
2015-11-30 9:39 ` Andreas Röhler
2015-11-30 15:53 ` Eli Zaretskii
2015-11-30 16:05 ` Paul Eggert
2015-11-26 16:08 ` Rasmus
2015-11-25 23:15 ` Mike Kupfer
2015-11-26 14:45 ` Richard Stallman
2015-11-27 0:43 ` Juri Linkov
2015-11-27 8:07 ` Eli Zaretskii
2015-11-27 23:24 ` Juri Linkov
2015-11-28 8:09 ` Eli Zaretskii
2015-11-27 8:02 ` Andreas Röhler
2015-11-27 8:57 ` Eli Zaretskii
2015-11-27 10:03 ` Artur Malabarba
2015-11-27 10:29 ` Eli Zaretskii
2015-11-27 10:47 ` Artur Malabarba
2015-11-29 9:08 ` Andreas Röhler
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=3719.1448674568@allegro.localdomain \
--to=m.kupfer@acm.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).