From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: gnus hangs on entry
Date: 01 Dec 1999 23:27:17 +0100 [thread overview]
Message-ID: <m3r9h6b8l6.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <kh74se4uehf.fsf@acme47.nineco.com>
lconrad@gamesville.com writes:
> This time, when I tried to get into gnus, I not only got the lisp
> error when I said to use the backup file, but I never managed to get
> into gnus when I said not to. I got all the usual messages in the
> mini-buffer about checking the servers and reading the active files,
> but then instead of showing me my groups, it just stops. This
> happened several times, both with xemacs and xemacs -nw. ^G does not
> interrupt it; the only way to stop it is to kill xemacs.
>
> So my questions are:
>
> Was anything I describe above a particularly stupid thing to
> do, and if so why?
Nope.
> What should I do now?
I'd try with a different version of (X)Emacs to see whether you get a
different result.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-12-01 22:27 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
1999-12-01 22:27 ` Lars Magne Ingebrigtsen [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=m3r9h6b8l6.fsf@quimbies.gnus.org \
--to=larsi@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).