From: "Richard M. Stallman" <rms@gnu.org>
Cc: teirllm@dms.auburn.edu, emacs-devel@gnu.org
Subject: Re: Overlong nodes in the Emacs Lisp Manual
Date: Sat, 13 Aug 2005 17:54:14 -0400 [thread overview]
Message-ID: <E1E43xG-0000O9-QY@fencepost.gnu.org> (raw)
In-Reply-To: <87acjmqtvo.fsf@jurta.org> (message from Juri Linkov on Sat, 13 Aug 2005 09:18:03 +0300)
Both the Emacs Manual and the Lisp Manual are distributed with Emacs,
so making a cross-reference is not a problem. Or do you mean hardcopy
versions of the Lisp Manual?
Yes.
Regexp syntax doesn't change too often, so syncing these manuals
between each other before the release would be enough - I see
no reason for the text about regexps to be different in both manuals.
I am sure there are differences that are intentional. Please
drop this issue.
Are there any tasks in FOR-RELEASE that you could do? Could you
perhaps split some of the longer nodes in the manual? I would like to
split every node that documents a specific technical topic and is
longer than 200 lines. 200 lines is still too long, for such a node,
but splitting the longer nodes is at least a start.
next prev parent reply other threads:[~2005-08-13 21:54 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
2005-08-12 19:58 ` Richard M. Stallman
2005-08-13 6:18 ` Juri Linkov
2005-08-13 21:54 ` Richard M. Stallman [this message]
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=E1E43xG-0000O9-QY@fencepost.gnu.org \
--to=rms@gnu.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).