From: Drew Adams <drew.adams@oracle.com>
To: rms@gnu.org, Stefan Kangas <stefan@marxist.se>
Cc: mattiase@acm.org, 41006@debbugs.gnu.org, rtm443x@googlemail.com
Subject: bug#41006: 26.3; regular expressions documentation
Date: Fri, 8 May 2020 09:49:11 -0700 (PDT) [thread overview]
Message-ID: <d82c7a38-63ec-4274-a4d2-f600da2b0834@default> (raw)
In-Reply-To: <E1jWt4k-0004uv-2l@fencepost.gnu.org>
> > My proposal is to include "how to use them" inside the chapter
> > called "Regular Expressions". Is there any reason not to do that?
>
> Now we have
>
> * Regular Expressions:: Describing classes of strings.
> * Regexp Search:: Searching for a match for a regexp.
>
> We could convert Regexp Search into a subsection under Regular
> Expressions. I don't see any harm in doing that.
I too agreed with that, and added:
In that case, in the section on search there'd need
to be some mention the ability to do regexp search,
and xrefs to the relevant "use" sections of the
regexp doc.
IOW, if regexp search is under regexps then the (other)
search section needs to link to the regexp-search topic.
> The Regexp Search node could come before, or after, the
> existing subsection, Regexp Functions. Which would be better?
Suggestion:
1. Some high-level description of regexps - an idea
of what they are and what you can use them for.
2. How to use them to match/search: regexp search.
3. Details of what they are - syntax, etc.
But the order between 2 & 3 could be the opposite.
What's important is for #1 to introduce both 2 & 3.
And of course links among topics, for people who
land on one of them out of the blue (e.g. by
googling and getting to the HTML manual on the web).
> Does anyone object to this change?
(Not I.)
next prev parent reply other threads:[~2020-05-08 16:49 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 19:06 bug#41006: 26.3; regular expressions documentation jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-03 3:40 ` Richard Stallman
2020-05-03 10:31 ` jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-03 13:07 ` Mattias Engdegård
2020-05-03 14:00 ` jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-03 20:08 ` Drew Adams
2020-05-03 20:31 ` Stefan Kangas
2020-05-04 1:00 ` Drew Adams
2020-05-05 2:56 ` Richard Stallman
2020-05-05 10:05 ` jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-05 16:51 ` Mattias Engdegård
2020-05-05 18:20 ` Stefan Kangas
2020-05-05 18:40 ` Drew Adams
2020-05-05 19:04 ` Stefan Kangas
2020-05-05 19:42 ` Drew Adams
2020-05-05 21:23 ` Stefan Kangas
2020-05-05 21:37 ` Drew Adams
2020-05-07 2:40 ` Richard Stallman
2020-05-09 3:48 ` Richard Stallman
2020-05-07 2:41 ` Richard Stallman
2020-05-07 3:17 ` Drew Adams
2020-05-08 2:51 ` Richard Stallman
2020-05-07 10:31 ` Stefan Kangas
2020-05-07 2:41 ` Richard Stallman
2020-05-07 3:18 ` Drew Adams
2020-05-07 10:32 ` Stefan Kangas
2020-05-08 2:49 ` Richard Stallman
2020-05-08 6:47 ` Eli Zaretskii
2020-05-08 10:10 ` Stefan Kangas
2020-05-08 10:31 ` Eli Zaretskii
2020-05-08 18:17 ` Stefan Kangas
2020-05-08 18:47 ` Eli Zaretskii
2020-05-08 20:09 ` Stefan Kangas
2020-05-08 10:04 ` jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-09 3:56 ` Richard Stallman
2020-05-08 16:49 ` Drew Adams [this message]
2020-05-09 3:53 ` Richard Stallman
2020-05-09 3:54 ` Richard Stallman
2020-05-07 2:41 ` Richard Stallman
2020-05-04 3:10 ` Richard Stallman
2020-05-04 9:13 ` jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-05 2:56 ` Richard Stallman
2020-05-05 10:02 ` jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-05 17:12 ` Mattias Engdegård
2020-05-05 17:40 ` Eli Zaretskii
2020-05-05 17:50 ` jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-05 18:09 ` Stefan Kangas
2020-05-05 18:23 ` Eli Zaretskii
2020-05-07 2:42 ` Richard Stallman
2022-04-29 12:22 ` Lars Ingebrigtsen
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=d82c7a38-63ec-4274-a4d2-f600da2b0834@default \
--to=drew.adams@oracle.com \
--cc=41006@debbugs.gnu.org \
--cc=mattiase@acm.org \
--cc=rms@gnu.org \
--cc=rtm443x@googlemail.com \
--cc=stefan@marxist.se \
/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.