all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kevin Ryde <user42@zip.com.au>
To: Glenn Morris <rgm@gnu.org>
Cc: 3818@emacsbugs.donarmstrong.com
Subject: bug#3818: 23.1.50; widget manual xref clickable text
Date: Sun, 12 Jul 2009 12:08:01 +1000	[thread overview]
Message-ID: <8763dypsam.fsf@blah.blah> (raw)
In-Reply-To: <h8d4868zwd.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sat, 11 Jul 2009 21:15:46 -0400")

Glenn Morris <rgm@gnu.org> writes:
>
> in the info directory in the Emacs build tree, and that seemed to work
> fine.

When it says "Not available to check" it means node names in those
manuals aren't checked.  The message doesn't show what node name(s) go
unchecked (only the filename).  Perhaps it should.  I suppressed that
deliberately to avoid a slew of messages (one for every link) when some
external manual is not available.

When I check I try to have external manuals available.  Just sticking
"/usr/share/info" after "." would get pretty close.  (In theory if you
had a full set of gnu manuals in a directory you could xref check them
all, though even then there might be a few manuals from friendly
external projects referred to ...).





      reply	other threads:[~2009-07-12  2:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <xfy6qvkjjm.fsf@fencepost.gnu.org>
2009-07-11  1:21 ` bug#3818: 23.1.50; widget manual xref clickable text Kevin Ryde
2009-07-11  3:10   ` bug#3818: marked as done (23.1.50; widget manual xref clickable text) Emacs bug Tracking System
     [not found]   ` <handler.3818.D3818.124728142722587.notifdone@emacsbugs.donarmstrong.com>
2009-07-11 22:09     ` bug#3818: 23.1.50; widget manual xref clickable text Kevin Ryde
2009-07-12  1:15       ` Glenn Morris
2009-07-12  2:08         ` Kevin Ryde [this message]

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=8763dypsam.fsf@blah.blah \
    --to=user42@zip.com.au \
    --cc=3818@emacsbugs.donarmstrong.com \
    --cc=rgm@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.