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: Info-scroll-prefer-subnodes default in Emacs.
Date: Wed, 25 Jun 2003 09:43:48 -0400	[thread overview]
Message-ID: <200306251343.h5PDhm805324@f7.net> (raw)

    One way is to have two kinds of
    menus, one that represents the document's structure and one that
    doesn't.  The index could say `* Index:' instead of `* Menu:'.  It
    would work the same in m but differently in SPC.  Karl, what do you
    think?

That sounds like a very clean idea to me, except ...
that new info files then won't be compatible with old Info readers.
We've gone to great lengths to avoid such incompatibilities in the past.

My idea along these lines was not as elegant, but it retains
compatibility: have makeinfo output a magic cookie (say ^H^[index^H^],
for the sake of argument, similar to the new cookie we use for images)
at the beginning of an index.  New info readers will recognize that, not
display it, and do the right thing.  Old info readers will display it,
which is ugly but not fatal -- the index entries would still work.

    Another way is to do the index using xrefs instead of menus.

Seems more verbose.

             reply	other threads:[~2003-06-25 13:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-25 13:43 Karl Berry [this message]
2003-06-26  5:30 ` Info-scroll-prefer-subnodes default in Emacs Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2003-06-24 13:26 Karl Berry
2003-06-20 13:55 Karl Berry
2003-06-23  1:57 ` Miles Bader
2003-06-20  1:19 Luc Teirlinck
2003-06-21  4:56 ` Richard Stallman
2003-06-24  2:55   ` Luc Teirlinck
2003-06-24  3:50     ` Luc Teirlinck
2003-06-24  3:56       ` Luc Teirlinck
2003-06-25  2:56       ` Richard Stallman
2003-06-24  4:12     ` Eli Zaretskii
2003-06-25  3:03       ` Luc Teirlinck
2003-06-25  2:57     ` 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=200306251343.h5PDhm805324@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).