From: garoth@gmail.com (Andrei Thorp)
Subject: [sup-talk] problems with Maildir and IMAP offline
Date: Tue, 14 Jul 2009 11:14:50 -0400 [thread overview]
Message-ID: <1247584404-sup-7126@Longbow> (raw)
In-Reply-To: <20090714150034.GA393@d228.scdc1.swarthmore.edu>
Excerpts from Tim Gray's message of Tue Jul 14 11:00:34 -0400 2009:
> On Tue 14, Jul'09 at 10:02 AM -0400, Andrei Thorp wrote:
> > Put this in a hook and it's automatic. That's the beauty of the
> > hook/multiple binary design.
>
> Honestly, if it's that easy, shouldn't it be configured like that out of the
> box?
People perhaps don't want this. It's slower, and a lot of folks probably
do no syncing back since all they use is sup anyway.
> > I'm not entirely sure why you want this. If you're worried about
> > failures, do they really happen? If you want to see the log, aren't you
> > already piping it? If you want notifications, you could hook them up to
> > happen in your sup hook (the one I described before) rather trivially
> > via notify-send.
>
> For use with other mail clients for one.
Understood. Makes sense in your use case. I don't really understand why
you'd want to use pine/mutt when you've already got sup though ;)
--
Andrei Thorp, Developer: Xandros Corp. (http://www.xandros.com)
next prev parent reply other threads:[~2009-07-14 15:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 21:20 Luis Cañas Díaz
2009-07-14 13:24 ` Andrei Thorp
[not found] ` <20090714134544.GD90157@d228.scdc1.swarthmore.edu>
2009-07-14 14:02 ` Andrei Thorp
2009-07-14 15:00 ` Tim Gray
2009-07-14 15:07 ` Ben Walton
2009-07-14 15:28 ` Tim Gray
2009-07-14 15:39 ` Andrei Thorp
2009-07-14 15:59 ` Tim Gray
2009-07-14 15:14 ` Andrei Thorp [this message]
2009-07-14 15:45 ` Tim Gray
2009-07-14 16:21 ` Israel Herraiz
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=1247584404-sup-7126@Longbow \
--to=garoth@gmail.com \
/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