From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: mattiase@acm.org, rms@gnu.org, 41006@debbugs.gnu.org,
rtm443x@googlemail.com
Subject: bug#41006: 26.3; regular expressions documentation
Date: Fri, 08 May 2020 13:31:28 +0300 [thread overview]
Message-ID: <83tv0qiupr.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmq9KiE7W1wSwEQvN2K6QEZivwuheqM0RxLT5269Wn41A@mail.gmail.com> (message from Stefan Kangas on Fri, 8 May 2020 03:10:45 -0700)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Fri, 8 May 2020 03:10:45 -0700
> Cc: mattiase@acm.org, 41006@debbugs.gnu.org, rtm443x@googlemail.com
>
> In the user manual, perhaps we could re-organize what we have now
> (excluding other subsections for the sake of brevity):
>
> * Searching and Replacement
> ** Regexp Search:: Search for match for a regexp.
> ** Regexps:: Syntax of regular expressions.
> ** Regexp Backslash:: Regular expression constructs starting with ‘\’.
> ** Regexp Example:: A complex regular expression explained.
>
> Into something like:
>
> * Searching and Replacement
> ** Regular Expression Search Search for match for a regexp.
> *** Regexp Syntax:: Syntax of regular expressions.
> *** Regexp Backslash:: Regular expression constructs starting with ‘\’.
> *** Regexp Example:: A complex regular expression explained.
Is "Regular Expression Search" just a parent node of its children, or
does it have content of its own (apart of the menu)? If the former,
we need a subsection about searching with regexps, after we describe
the regular expressions. If the latter, then do you suggest to
describe the search before describing the regexps themselves?
next prev parent reply other threads:[~2020-05-08 10:31 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 [this message]
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
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
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=83tv0qiupr.fsf@gnu.org \
--to=eliz@gnu.org \
--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 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).