all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: bug-gnu-emacs@gnu.org
Subject: Info mode - inconsistent display of cross-references
Date: Sat, 25 Aug 2007 08:23:50 +0000	[thread overview]
Message-ID: <20070825082349.GA2640@muc.de> (raw)

Hi, Emacs!

In Emacs 22.1, display the page "Getting Started" in the CC Mode manual.

The second paragraph is displayed thusly:

    You should probably start by skimming through the entire chapter
    see Commands to get an overview of CC Mode's capabilities.
    ^^^^

.  The "see " in "see Commands" is an artifact of the Info display code,
and is horrible, disgusting and ghastly.  It should not appear.

A little bit lower down on the same page, we have:

                                                            A list of
    the available styles and their descriptions can be found in
    Built-in Styles.
^^^^

Here there is no obtrusive "see " in front of "Built-in Styles", and this
is all right.

However, in the raw file  ...../info/ccmode, both of these xrefs are
coded the same way, namely "*Note Commands::" and "*Note
Built-in Styles::".  (Well, there's a linefeed in the second one, but
they're otherwise the same.)

In the source file, cc-mode.texi, both xrefs are coded correctly with the
@ref{} construct.

Whatever's going on here is surely a bug.  Both of these should be
displayed the same, _without_ the obtrusive "see ".  If this can't be
done because of limitiations in the Info format, it would surely be less
bad to display the raw "*Note Commands", since this is being honest about
Info and doesn't make the writer of the manual look incompetent.

-- 
Alan Mackenzie (Ittersbach, Germany).

             reply	other threads:[~2007-08-25  8:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-25  8:23 Alan Mackenzie [this message]
2007-08-25 19:51 ` Info mode - inconsistent display of cross-references Stephen Berman
2007-12-22 21:08 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070825082349.GA2640@muc.de \
    --to=acm@muc.de \
    --cc=bug-gnu-emacs@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.