From: Jason L Tibbitts III <tibbs@math.uh.edu>
To: ding@gnus.org
Subject: Re: Debugging extremely long IMAP folder exit times
Date: Thu, 25 Jul 2019 15:27:05 -0500 [thread overview]
Message-ID: <ufa8ssllv1i.fsf@epithumia.math.uh.edu> (raw)
In-Reply-To: <87wog56flq.fsf@uwo.ca> (Dan Christensen's message of "Thu, 25 Jul 2019 16:09:37 -0400")
>>>>> "DC" == Dan Christensen <jdc@uwo.ca> writes:
DC> If you haven't yet cleared the data, it would be interesting to see
DC> if there are fixes that don't clear the remote marks and flags (even
DC> though you don't seem to have any in this case).
I haven't yet, but somehow the problem has fixed itself in the
meantime. Just checked .newsrc.eld and the unexist info is filled in.
So when I have this problem again, I will go ahead and try both of your
suggestions and see if they help.
- J<
prev parent reply other threads:[~2019-07-25 20:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 18:34 Jason L Tibbitts III
2019-07-18 20:31 ` Andreas Schwab
2019-07-18 22:15 ` Jason L Tibbitts III
2019-07-22 17:08 ` Jason L Tibbitts III
2019-07-22 17:54 ` Eric Abrahamsen
2019-07-22 18:44 ` Jason L Tibbitts III
2019-07-22 23:25 ` Eric Abrahamsen
2019-07-24 23:54 ` Jason L Tibbitts III
2019-07-25 20:09 ` Dan Christensen
2019-07-25 20:27 ` Jason L Tibbitts III [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=ufa8ssllv1i.fsf@epithumia.math.uh.edu \
--to=tibbs@math.uh.edu \
--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).