From: Dave Love <fx@gnu.org>
Cc: wmperry@gnu.org, emacs-devel@gnu.org
Subject: Re: New files url.texi and org.texi
Date: Sun, 12 Dec 2004 19:14:52 +0000 [thread overview]
Message-ID: <rzqu0qrxr9v.fsf@loveshack> (raw)
In-Reply-To: <200412080412.iB84CUP06430@raven.dms.auburn.edu> (Luc Teirlinck's message of "Tue, 7 Dec 2004 22:12:30 -0600 (CST)")
Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> Is there a reason why all the standard things that need to be done to
> make a new .info file show up in the user's dir have not been done for
> the new files url.texi and org.texi?
I can't answer that, but the URL manual may not be in a sufficiently
useful state to get installed -- as in installed for users, rather
than in CVS. It's a long time since I did anything with it, but if I
remember correctly, it's mostly placeholders unless someone has worked
on it since.
> Two @xref's to emacs-mime need to be replaced with @inforef's or we
> get, in the hardcopy output:
>
> See <undefined> [(emacs-mime)Top], page <undefined>.
It shouldn't be replaced, according to my reading of the Texinfo
manual; there clearly could be a printed copy of the MIME manual if
there's one for URL. I think the xrefs just need fixing. I probably
wrote them, and I suspect it wasn't clear how to fill in all the
fields. I suspect there were incompatible versions of emacs-mime.texi
around at the time.
By the way, I think that the emacs-mime manual to which it refers
needs work. If I remember correctly, it mixes up library and
user-level features, and doesn't document some of the features that
URL, for instance, needs.
next prev parent reply other threads:[~2004-12-12 19:14 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 [this message]
2004-12-12 20:00 ` Luc Teirlinck
2004-12-13 20:29 ` Dave Love
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=rzqu0qrxr9v.fsf@loveshack \
--to=fx@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=wmperry@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).