From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Can't retreat either
Date: Fri, 07 Sep 2001 12:44:03 +0200 [thread overview]
Message-ID: <vaf1yljb7rg.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m1u1yf983z.fsf@reader.newsguy.com> (Harry Putnam's message of "06 Sep 2001 17:10:12 -0700")
Harry Putnam <reader@newsguy.com> writes:
> How can I back up gracefully to a gnus that didn't use this code. Can
> I simply remove the section from .newsrc.eld that contains
> gnus-correct-length?
That's right, you can just remove the (setq gnus-format-spec ...)
statement. I think this comes from (gnus-compile) in your .gnus file,
so it will be recreated the next time Gnus starts.
kai
--
Symbol's function definition is void: signature
prev parent reply other threads:[~2001-09-07 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 0:10 Harry Putnam
2001-09-07 6:50 ` ShengHuo ZHU
2001-09-07 14:30 ` Harry Putnam
2001-09-07 10:44 ` Kai Großjohann [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=vaf1yljb7rg.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.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).