Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: davmail hangs *after* retrieving pop email from Exchange server
Date: Thu, 27 May 2021 09:59:06 -0700	[thread overview]
Message-ID: <874keow1t1.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87pmxcunmb.fsf@ucl.ac.uk>

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> On Thursday, 27 May 2021 at 08:40, Eric Abrahamsen wrote:
>> I think the usual thing to do would be M-x toggle-debug-on-quit, then
>> get to the hang, then C-g. You should see a traceback telling you what
>> Emacs was doing when you quit it.
>
> Thank you for this suggestion.  However, I've tried this already (debug
> on error and debug on quit are my first ports of call...) 

I should have known that :)

> and I do not get a backtrace when I hit C-g but simply continues with
> the rest of the email & news retrieval. This does suggest a network
> hang of some sort but I don't understand why/how. These types of
> problems are the most frustrating in gnus (maybe Emacs generally?).

They are frustrating! And my guess is that a `condition-case' somewhere
is handling the `quit' -- all of a sudden this sort of thing is
responsible for like 90% of my Emacs debugging. It's even possible that
it's the same location as Hirotaka Honda has run in to: mail splitting
inside `nnmail-get-new-mail-1'. Do you see anything in *Messages*? How
about with `gnus-verbose-backends' set to 10? Or try stepping thrhough
`nnmail-get-new-mail-1' and see if anything "bad" happens...



  reply	other threads:[~2021-05-27 16:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27 13:04 Eric S Fraga
2021-05-27 13:14 ` Dan Christensen
2021-05-27 22:12   ` Eric S Fraga
2021-05-27 15:40 ` Eric Abrahamsen
2021-05-27 16:50   ` Eric S Fraga
2021-05-27 16:59     ` Eric Abrahamsen [this message]
2021-05-27 18:49       ` Eric S Fraga
2021-05-27 18:59         ` Eric Abrahamsen
2021-05-27 17:03   ` Eric S Fraga

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=874keow1t1.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).