From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: info-xref empty filenames
Date: Tue, 24 Feb 2004 03:34:30 +0200 [thread overview]
Message-ID: <8765dxclax.fsf@mail.jurta.org> (raw)
In-Reply-To: 87wu6nx3a5.fsf@zip.com.au
Kevin Ryde <user42@zip.com.au> writes:
>> * info-xref.el (info-xref-check-buffer): Report empty filename parts.
>> Remove spurious node duplicate suppression, doesn't work, not wanted.
>> (info-xref-output): Take format style args.
>
> I'd like to re-propose this addition to my info-xref. I think it got
> lost while the cvs was down.
Since your papers are apparently OK, I want to suggest you to
implement a new checking rule in info-xref.el. Customization
definitions (defcustom) can have the keyword `:link' with a link
to an Info node in a `custom-manual' or `info-link' field. I've
already found some broken links to Info nodes in some defcustoms,
but having a function in info-xref.el to perform such checks will
help to catch them all.
--
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2004-02-24 1:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 23:23 info-xref empty filenames Kevin Ryde
2004-02-16 0:43 ` Kevin Ryde
2004-02-24 1:34 ` Juri Linkov [this message]
2004-02-24 22:36 ` Kevin Ryde
2004-03-11 0:09 ` Kevin Ryde
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=8765dxclax.fsf@mail.jurta.org \
--to=juri@jurta.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).