unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: karl@freefriends.org (Karl Berry)
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] ignoring Info extensions
Date: Fri, 2 Apr 2004 20:25:54 -0500	[thread overview]
Message-ID: <200404030125.i331Ps326653@f7.net> (raw)
In-Reply-To: <874qs2netc.fsf@mail.jurta.org>

    Are two menus allowed in one node, or should we fix Info readers?

One menu.  I changed texinfo.txi at some point to say this:

  A menu must be located at the end of a node, without any regular text
  or additional commands between the @code{@@end menu} and the beginning
  of the next node.  (As a consequence, there may be at most one menu in
  a node.)

At some point I'll add a warning to makeinfo when this condition isn't
met.

    2. If a menu has an empty item (a single `*' on the whole line)

This also seems invalid to me.  There's no provision for "empty" menu
items.

    then the previous menu item is displayed in Info-title-1-face.
    An example of such menu is the START-INFO-DIR-ENTRY of coreutils.info.

I don't see it.  I'm looking at coreutils 5.2.1.

    Perhaps a line should be displayed in Info-title-1-face only
    if the following line has two or more `*'.

I don't understand?  Why would a line start with two *'s?

  reply	other threads:[~2004-04-03  1:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-11 19:47 resend: [PATCH] ignoring Info extensions Jan Nieuwenhuizen
2004-03-14  7:39 ` Eli Zaretskii
2004-03-14 12:53   ` Jan Nieuwenhuizen
2004-03-29  7:57   ` Jan Nieuwenhuizen
2004-03-31 20:56     ` Juri Linkov
2004-04-01  2:01       ` Karl Berry
2004-04-01  5:53         ` Eli Zaretskii
2004-04-01 16:33         ` Juri Linkov
2004-04-01 19:53           ` Eli Zaretskii
2004-04-02  3:27             ` Juri Linkov
2004-04-02  7:47               ` Eli Zaretskii
2004-04-03  1:30               ` Richard Stallman
2004-04-02  1:50           ` Karl Berry
2004-04-02  3:32             ` Juri Linkov
2004-04-02 14:16               ` Karl Berry
2004-04-02 18:19                 ` Juri Linkov
2004-04-02 19:28                   ` Eli Zaretskii
2004-04-02 21:38                     ` Juri Linkov
2004-04-03  0:19                     ` Karl Berry
2004-04-02 19:29                 ` Eli Zaretskii
2004-04-02  7:43             ` Eli Zaretskii
2004-04-02 21:47         ` Juri Linkov
2004-04-03  1:25           ` Karl Berry [this message]
2004-04-03  4:56             ` Juri Linkov
2004-04-03  9:05             ` Eli Zaretskii
2004-04-03 23:39           ` Richard 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=200404030125.i331Ps326653@f7.net \
    --to=karl@freefriends.org \
    --cc=emacs-devel@gnu.org \
    /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).