From: Norbert Koch <n.koch@eai-delta.de>
Subject: Gnus Info Files (WinNT)
Date: 15 Nov 1999 10:08:34 +0100 [thread overview]
Message-ID: <uu2mom8a5.fsf@eai-delta.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 441 bytes --]
Hi!
I can't create the info files from the texi files using the commands
given in the Makefile. I've succeeded in creating them using the
command given in XEmacs Makefile (by Adrian Aichner
<aichner@ecf.teradyne.com>):
$(EMACS) -no-site-file -no-init-file -batch -l texinfmt \
-f batch-texinfo-format
It's rilly noisy, though.
I had to change gnus.texi (@var{@dots{}} results in @DOTS{} which
can't be handled by texinfo):
norbert.
[-- Attachment #2: gnus.texi change --]
[-- Type: text/plain, Size: 1483 bytes --]
Index: gnus.texi
===================================================================
RCS file: /usr/local/cvsroot/gnus/texi/gnus.texi,v
retrieving revision 5.114
diff -u -r5.114 gnus.texi
--- gnus.texi 1999/11/12 23:42:16 5.114
+++ gnus.texi 1999/11/15 09:09:12
@@ -10728,15 +10728,15 @@
name. Normal regexp match expansion will be done. See below for
examples.
-@item
-@code{(@var{field} @var{value} @var{[- restrict [- restrict [@dots{}]]]}
-@var{split})}: If the split is a list, the first element of which is a
-string, then store the message as specified by @var{split}, if header
-@var{field} (a regexp) contains @var{value} (also a regexp). If
-@var{restrict} (yet another regexp) matches some string after
-@var{field} and before the end of the matched @var{value}, the
-@var{split} is ignored. If none of the @var{restrict} clauses match,
-@var{split} is processed.
+@item
+@code{(@var{field} @var{value} [- @var{restrict} [- @var{restrict}
+[@dots{}]]] @var{split})}: If the split is a list, the first element
+of which is a string, then store the message as specified by
+@var{split}, if header @var{field} (a regexp) contains @var{value}
+(also a regexp). If @var{restrict} (yet another regexp) matches some
+string after @var{field} and before the end of the matched
+@var{value}, the @var{split} is ignored. If none of the @var{restrict}
+clauses match, @var{split} is processed.
@item
@code{(| @var{split}@dots{})}: If the split is a list, and the first
next reply other threads:[~1999-11-15 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-15 9:08 Norbert Koch [this message]
1999-11-15 18:18 ` Rene Matteau
1999-11-15 19:33 ` Hans de Graaff
1999-11-15 21:49 ` Christophe Cuq
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=uu2mom8a5.fsf@eai-delta.de \
--to=n.koch@eai-delta.de \
/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).