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 03:56:06 -0500	[thread overview]
Message-ID: <E1RjoXu-0001Ad-Ls@fencepost.gnu.org> (raw)
In-Reply-To: <EEC0CBC522044BD4AE4ACF43BCA4A91D@us.oracle.com> (drew.adams@oracle.com)

> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Sat, 7 Jan 2012 22:40:25 -0800
> 
> There are a few cross references such as this in the `Info' manual: "see
> Overview of Texinfo(texinfo)".  The Texinfo manual is not included with
> Emacs.  These links are thus broken.

We also have links to other manuals provided by other projects: Make,
glibc, and Aspell, for example.  Manuals of other GNU projects do the
same; e.g. the Texinfo manuals include references to Emacs.  There's
nothing we can do about this; avoiding such links would make the
manual less useful.

A reader does not _have_ to follow every hyperlink she sees, only
those she is really interested in.  A reader who really is interested
in the details of how Info files are generated, will need to install
the Texinfo package which brings the manual with it.

(You can have it too, a Windows port is available.  Drop me a note if
you want a URL.)

> While it is not absolutely necessary that the links actually work, it
> would be far better if the manual used only links that work.  In this
> case, a different manual could be used - one that is included with
> Emacs.

Are you suggesting to have some version of Texinfo manual as part of
the Emacs package?  That sounds like a strange proposal: it would lead
to massive duplication of effort or to excessive interdependencies
between largely independent projects.  Cf. the (still on-going)
discussion about "GnuTLS and W32".

What could be useful is to enhance info.el to give some indication
that a given hyperlink points to a manual that is not available.  If
this is what your report is about, or if it could be satisfied by such
a change, then I agree; otherwise I think we should close this report
with no further action.





  reply	other threads:[~2012-01-08  8:56 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 [this message]
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
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=E1RjoXu-0001Ad-Ls@fencepost.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.