all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 10451@debbugs.gnu.org
Subject: bug#10451: 24.0.92; Bad cross reference in Info manual
Date: Sun, 08 Jan 2012 21:06:02 +0200	[thread overview]
Message-ID: <83zkdydnfp.fsf@gnu.org> (raw)
In-Reply-To: <A73DA5CED5F948D7948F37216821A1E6@us.oracle.com>

> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <10451@debbugs.gnu.org>
> Date: Sun, 8 Jan 2012 10:56:54 -0800
> 
> This is that "real cross-reference to Texinfo", which you mention:
> 
> "However, Emacs normally hides some other text in cross-references.
>  If you put your mouse over the cross reference, then the information
>  appearing in a separate box (tool tip) or in the echo area will show
>  the full cross-reference including the file name and the node name of
>  the cross reference.  If you have a mouse, just leave it over the cross
>  reference *Note Overview of Texinfo: (texinfo)Top, and watch what
>  happens."

This is not the one I had in mind.  If you are talking about this one,
then there's another problem: this manual also comes with the Texinfo
package.  If that reference is changed to point to the Emacs manual,
it will be broken for someone who installs the Texinfo manual and
doesn't have the Emacs manual installed.





  reply	other threads:[~2012-01-08 19:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-08  6:40 bug#10451: 24.0.92; Bad cross reference in Info manual Drew Adams
2012-01-08  8:56 ` Eli Zaretskii
2012-01-08 15:29   ` Drew Adams
2012-01-08 18:12     ` Eli Zaretskii
2012-01-08 18:56       ` Drew Adams
2012-01-08 19:06         ` Eli Zaretskii [this message]
2012-01-08 19:19           ` Drew Adams
2012-01-08 22:34   ` Richard Stallman
2013-02-08 21:09     ` Drew Adams
2014-02-09  5:25       ` Lars Ingebrigtsen

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=83zkdydnfp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=10451@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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.