Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: gnus hangs emacs at start
Date: Mon, 30 Dec 2002 19:46:58 +0100	[thread overview]
Message-ID: <84of73s5st.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m2smwfxvj4.fsf@hartford-hwp.com>

Haines Brown <brownh@hartford-hwp.com> writes:

> I find that starting .gnus, regardless of whether there are any gnus
> files in ~/ can randomly hang emacs. 
>
> My work-aroud is:
>
>         Mx toggle-debug-on-quit
>         C-g
>         c

If you have several servers configured and Gnus can't connect to one
of them, then you can use C-g to skip that server.

So maybe C-g works even without debugging turned on.

I suggest to (setq gnus-verbose 10 gnus-verbose-backends 10), then
you can better see what Gnus is doing.

-- 
Ambibibentists unite!


      parent reply	other threads:[~2002-12-30 18:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <pan.2002.12.22.15.57.06.893701@hartford-hwp.com>
2002-12-23 17:34 ` Dave Bennett
2002-12-28 15:36   ` Haines Brown
     [not found]     ` <m2smwfxvj4.fsf@hartford-hwp.com>
2002-12-30 18:46       ` 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=84of73s5st.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@uni-duisburg.de \
    /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).