unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: teirllm@dms.auburn.edu, emacs-devel@gnu.org
Subject: Re: Overlong nodes in the Emacs Lisp Manual
Date: Fri, 12 Aug 2005 12:59:32 +0300	[thread overview]
Message-ID: <8764ubzd03.fsf@jurta.org> (raw)
In-Reply-To: <E1E3JsZ-00022M-5U@fencepost.gnu.org> (Richard M. Stallman's message of "Thu, 11 Aug 2005 16:42:19 -0400")

> I will look at splitting these now:
>
>     361 (info "(emacs)Regexps")

Please note that in the Emacs Lisp Reference Manual there are already
four shorter nodes

(info "(elisp)Syntax of Regexps")
(info "(elisp)Regexp Special")
(info "(elisp)Regexp Backslash")
(info "(elisp)Regexp Example")

that almost completely duplicate the text in (emacs)Regexps.

I think regular expressions is a user-level feature.  So these
nodes should be moved to the Emacs User Manual, and text from
(emacs)Regexps should be merged with text in these four nodes.

Then in the Emacs Lisp Reference Manual only the node
(info "(elisp)Regexp Functions") would remain with a cross-reference
to the Emacs User Manual for description of regular expressions.

-- 
Juri Linkov
http://www.jurta.org/emacs/

  reply	other threads:[~2005-08-12  9:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-09 15:19 Overlong nodes in the Emacs Lisp Manual Richard M. Stallman
2005-08-09 19:11 ` Luc Teirlinck
2005-08-10 15:37   ` Richard M. Stallman
2005-08-11  0:27     ` Juri Linkov
2005-08-11 17:15       ` Thien-Thi Nguyen
2005-08-11 20:42       ` Richard M. Stallman
2005-08-12  9:59         ` Juri Linkov [this message]
2005-08-12 19:58           ` Richard M. Stallman
2005-08-13  6:18             ` Juri Linkov
2005-08-13 21:54               ` Richard M. Stallman
2005-08-11 20:42       ` Richard M. Stallman

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=8764ubzd03.fsf@jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@gnu.org \
    --cc=teirllm@dms.auburn.edu \
    /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).