From: Jesper Harder <harder@myrealbox.com>
Subject: Re: Setting gnus-list-identifiers on a per-group basis
Date: Tue, 28 May 2002 21:59:54 +0200 [thread overview]
Message-ID: <m3k7pot551.fsf@defun.localdomain> (raw)
In-Reply-To: <g00c2hqv.fsf@morpheus.demon.co.uk>
Paul Moore <gustav@morpheus.demon.co.uk> writes:
> I did some searching around, and had a go. The upgrade was pretty
> painless in the end. But I'm still not particularly clear as to what's
> new. The manual doesn't include a "New features in Oort Gnus" section,
> as far as I can tell, and I can't see a News file with any sort of
> summary.
Look for the file 'GNUS-NEWS' in the top directory of the Gnus
distribution.
> Also, when I tried to format the manual for printing, I got errors
> (undefined control sequence @iflatex). This is using texi2dvi (both
> for DVI and PDF output) and using "raw" (PDF)LaTeX and TeX. (The
> latest versions from the MikTeX distribution for Windows).
Yes, you have to use the makefile to generate the dvi version. If you
have cygwin, it might work on Windows.
Otherwise I think something like this
emacs gnus.texi -l infohack.el -f infohack-remove-unsupported
should give you a version, which can be processed with texi2dvi.
prev parent reply other threads:[~2002-05-28 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-26 12:49 Paul Moore
2002-05-27 4:30 ` Paul Jarc
[not found] ` <8z65dafj.fsf@morpheus.demon.co.uk>
[not found] ` <4rgtd9yc.fsf@morpheus.demon.co.uk>
[not found] ` <g00c2hqv.fsf@morpheus.demon.co.uk>
2002-05-28 19:59 ` Jesper Harder [this message]
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=m3k7pot551.fsf@defun.localdomain \
--to=harder@myrealbox.com \
/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).