From: Alan Shutko <ats@acm.org>
Cc: ding@gnus.org
Subject: Re: Utter frustration
Date: 21 Sep 1998 11:05:03 -0500 [thread overview]
Message-ID: <m367eh78pc.fsf@hubert.wuh.wustl.edu> (raw)
In-Reply-To: Hrvoje Niksic's message of "21 Sep 1998 17:44:39 +0200"
>>>>> "H" == Hrvoje Niksic <hniksic@srce.hr> writes:
H> I cannot believe this is happening. I'm seriously considering
H> moving to slrn. Or tin. Or PINE. Or anything that would stop the
H> pain.
Sure, that would help. You'd still have to edit the newsrc for those.
So, try this. Make gnus write out a .newsrc as well as a .eld. Edit
the .newsrc (easy with a quick macro and M-x apply). Restart gnus.
Gnus should read both, with the article numbers in the .newsrc taking
precedence (because it's newer).
--
Alan Shutko <ats@acm.org> - By consent of the corrupted
Never argue with a fool -- people might not be able to tell the difference.
next prev parent reply other threads:[~1998-09-21 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-21 15:44 Hrvoje Niksic
1998-09-21 16:05 ` Alan Shutko [this message]
1998-09-21 16:07 ` Jan Vroonhof
1998-09-21 17:31 ` Per Abrahamsen
1998-09-21 17:43 ` Hrvoje Niksic
1998-09-23 20:14 ` Lars Magne Ingebrigtsen
1998-09-29 13:29 ` Christopher Davis
1998-10-01 3:10 ` Lars Magne Ingebrigtsen
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=m367eh78pc.fsf@hubert.wuh.wustl.edu \
--to=ats@acm.org \
--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).