GNU bug report logs - #41006
26.3; regular expressions documentation

Previous Next

Full log

View this message in rfc822 format

From: Richard Stallman <rms <at> gnu.org>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: mattiase <at> acm.org, 41006 <at> debbugs.gnu.org, rtm443x <at> googlemail.com
Subject: bug#41006: 26.3; regular expressions documentation
Date: Thu, 07 May 2020 22:49:22 -0400

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > 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.

The Regexp Search node could come before, or after, the
existing subsection, Regexp Functions.  Which would be better?

Does anyone object to this change?


Meanwhile, the node Regexp Search is 230 lines long.
Index entries pointing to such a long node are not
very helpful.  It would be good to subdivide that
(soon to be) subsection into several subsubsections.

This kind of splitting job calls for creativity,
perhaps reordering material in the node.

Splitting a node doesn't stop you from reading it as a whole.
If you visit in Info a node that has subnodes, 
you can read it and its subnodes sequentially
just by typing SPC repeatedly.

-- 
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.