Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: gnus in emacs 26 ok?
Date: Tue, 04 Sep 2018 17:15:18 +0200	[thread overview]
Message-ID: <87musxi9a1.fsf@delle7240.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <smubm9fjxox.fsf@linuxpal.mit.edu>

On Sunday,  2 Sep 2018 at 19:18, Greg Troxel wrote:
> I realize I should set debug-on-error and figure out what's going on,
> but I don't know how to deal with ^G not working.

Can't help directly except to say that when gnus hangs and doesn't want
to be interrupted via ^g, it's usually doing a network access to an imap
account.  Anecdotally.  My experience is that imap access is not quite
robust enough generally but have no idea why or how it could be made
better.

-- 
Eric S Fraga via Emacs 27.0.50 & org 9.1.13 on Debian buster/sid




  parent reply	other threads:[~2018-09-04 15:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-02 23:18 Greg Troxel
2018-09-04 14:12 ` Eric Abrahamsen
2018-09-04 15:15 ` Eric S Fraga [this message]
2018-09-04 23:25 ` Greg Troxel
2018-09-05 13:25   ` Filipp Gunbin
2018-09-05 14:14     ` Greg Troxel

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=87musxi9a1.fsf@delle7240.chemeng.ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --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).