From: Dave Love <fx@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: New files url.texi and org.texi
Date: Mon, 13 Dec 2004 20:29:13 +0000 [thread overview]
Message-ID: <rzqy8g2vt5y.fsf@loveshack> (raw)
In-Reply-To: 200412122000.iBCK0n418370@raven.dms.auburn.edu
Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> Are there _published_ printed versions of the MIME and URL manuals
> available? To me, @xref would suggest that there are.
I don't understand why.
> The user can always produce hardcopy _himself_ using texi2dvi.
> (Which is one of the reasons why we care about hardcopy even if
> there is no published manual.)
Of course, but I've no idea why that means you shouldn't use
@{x,px,}ref. I'm pretty sure I confirmed with rms that external
references should use the five-arg version of the @*ref commands when
I was linking the extra manuals from the Emacs manual.
> As I see it, @inforef means that there is no published
> manual, so we refer to the info file.
That's not what the manual says about it, and as it refers to an
Info-only file, it isn't appropriate if you're producing HTML manuals.
(I assume @inforef was intended for stuff that wasn't produced from
Texinfo source.)
next prev parent reply other threads:[~2004-12-13 20:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 4:12 New files url.texi and org.texi Luc Teirlinck
2004-12-08 4:39 ` Luc Teirlinck
2004-12-08 22:15 ` Richard Stallman
2004-12-12 19:14 ` Dave Love
2004-12-12 20:00 ` Luc Teirlinck
2004-12-13 20:29 ` Dave Love [this message]
2004-12-14 3:26 ` Luc Teirlinck
2004-12-14 19:11 ` Dave Love
2004-12-14 14:21 ` Robert J. Chassell
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=rzqy8g2vt5y.fsf@loveshack \
--to=fx@gnu.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).