From: ezyang@MIT.EDU (Edward Z. Yang)
Subject: [sup-talk] IMAP alternative for Sup?
Date: Fri, 12 Jun 2009 10:14:26 -0400 [thread overview]
Message-ID: <1244815945-sup-5020@javelin> (raw)
In-Reply-To: <1244812462-sup-9446@joe-wolfels-power-mac-g5.local>
Excerpts from Joe W?lfel's message of Fri Jun 12 09:21:11 -0400 2009:
> Also, I noticed that Sup's polling mechanism no longer locks up. With IMAP I
> used to have to restart Sup on occasion. Now that doesn't seem to happen. I'm
> not sure if that's relevant to the that other sup-talk thread on locking but
> maybe it's helpful info .
This is probably because OfflineIMAP polls more frequently. I've had good
results getting rid of the lock up by decreasing Sup's polling time (unfortunately
it's hard-coded in Sup).
Cheers,
Edward
next prev parent reply other threads:[~2009-06-12 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 17:21 Joe Wölfel
2009-06-10 17:25 ` Edward Z. Yang
2009-06-12 13:21 ` Joe Wölfel
2009-06-12 14:14 ` Edward Z. Yang [this message]
2009-06-12 14:34 ` Ben Walton
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=1244815945-sup-5020@javelin \
--to=ezyang@mit.edu \
/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