From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: gnus hangs on entry
Date: 30 Nov 1999 18:48:24 +0100 [thread overview]
Message-ID: <vafvh6jvpjr.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: lconrad@gamesville.com's message of "30 Nov 1999 11:32:44 -0500"
lconrad@gamesville.com writes:
> Was anything I describe above a particularly stupid thing to
> do, and if so why?
I don't think you did something really stupid. Hm. I suggest that
you have a look at your ~/.newsrc, ~/.newsrc.eld, ~/.gnus,
~/.newsrc-dribble and so on to see if there is any garbage in one of
those files.
The only thing different is that I might have investigated what Gnus
didn't like about the auto-save file that it caused to hang, rather
than just saying no the second time.
kai
--
because I couldn't think of a good beginning.
next prev parent reply other threads:[~1999-11-30 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-30 16:32 lconrad
1999-11-30 17:48 ` Kai Großjohann [this message]
1999-12-01 22:27 ` 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=vafvh6jvpjr.fsf@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).