From: Karl Berry <karl@freefriends.org>
Cc: didier@xemacs.org, xemacs-beta@xemacs.org, ding@gnus.org
Subject: Re: XEmacs info.el and PGnus info files
Date: Tue, 30 May 2000 10:04:32 -0400 [thread overview]
Message-ID: <200005301404.KAA23827@freefriends.org> (raw)
.info is not mandatory. The texinfo distribution itself uses texinfo-1,
texinfo-2, etc.
It also supports numerous other extensions, mostly for DOS.
static char *info_suffixes[] = {
".info",
"-info",
"/index",
".inf", /* 8+3 file on filesystem which supports long file names */
#ifdef __MSDOS__
/* 8+3 file names strike again... */
".in", /* for .inz, .igz etc. */
".i",
#endif
"",
NULL
};
static COMPRESSION_ALIST compress_suffixes[] = {
{ ".gz", "gunzip" },
{ ".bz2", "bunzip2" },
{ ".z", "gunzip" },
{ ".Z", "uncompress" },
{ ".Y", "unyabba" },
#ifdef __MSDOS__
{ "gz", "gunzip" },
{ "z", "gunzip" },
#endif
{ (char *)NULL, (char *)NULL }
};
next reply other threads:[~2000-05-30 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-30 14:04 Karl Berry [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-05-29 14:44 Didier Verna
2000-05-29 15:26 ` François Pinard
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=200005301404.KAA23827@freefriends.org \
--to=karl@freefriends.org \
--cc=didier@xemacs.org \
--cc=ding@gnus.org \
--cc=xemacs-beta@xemacs.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.
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 NNTP newsgroup(s).