unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Thu, 11 Aug 2005 16:42:21 -0400	[thread overview]
Message-ID: <E1E3Jsb-00022U-Cu@fencepost.gnu.org> (raw)
In-Reply-To: <87oe852x47.fsf@jurta.org> (message from Juri Linkov on Thu, 11 Aug 2005 03:27:12 +0300)

    I think not only long nodes should be checked, but also the shortest
    nodes too.  For example, the node `(elisp)Inverse Video' has 11 lines
    and documents a semi-obsolete option `inverse-video'.  Its menu item
    description in its upper node is too general:

      * Inverse Video    Specifying how the screen looks.

I think you are right.  In this case, I simply deleted the node,
since the variable it documented is basically obsolete.

Could you take a look the remaining nodes that are 14 lines or less,
and see if you can find good places to merge them into?
Ignore these
    14 (info "(elisp)Window Configuration Type")
    14 (info "(elisp)Hash Table Type")
    14 (info "(elisp)Frame Configuration Type")
    13 (info "(elisp)Keymap Type")
which probably should not be combined,
and don't try desperately hard.

      parent reply	other threads:[~2005-08-11 20:42 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
2005-08-11 20:42       ` Richard M. Stallman [this message]

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=E1E3Jsb-00022U-Cu@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).