From: lists+sup@protozoic.com (Tim Gray)
Subject: [sup-talk] problems with Maildir and IMAP offline
Date: Tue, 14 Jul 2009 11:00:34 -0400 [thread overview]
Message-ID: <20090714150034.GA393@d228.scdc1.swarthmore.edu> (raw)
In-Reply-To: <1247580020-sup-9946@Longbow>
On Tue 14, Jul'09 at 10:02 AM -0400, Andrei Thorp wrote:
> I'm forwarding a summary of your message with my replies to the mailing
> list. It seems like you replied to me only by accident?
Whoops. I didn't realize this list didn't have reply-to set. Thanks.
> Again, see sup-sync-back -- it does indeed have _some_ ability to write
> its state back to the source.
To me, this is a vital feature of any mail client. I'll look into it, but I
would really like this to be fully integrated into my mail client. And from
I've read, this isn't something that's going to happen.
Sometimes I need to use mutt/pine. Sometimes webmail. Most importantly, I
want all my mail in a form that is easy to backup, human readable, and can
be manipulated with standard utilities. Maildir fits the bill.
I think it'd be fantastic if there was a mail client that allowed you to
sort by folders, but also provided a sup-like view that laid on top if/when
you needed.
> 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?
> 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. It's kind of nice having my IMAP
syncing separate from the mail client. I'm sure I could run it
automatically via cron, but then you'd have to give up the quick refresh
capability (minor) and the IDLE mode. Sure, I could pipe the output
somewhere else, but wouldn't that accomplish the same thing as just looking
at the output already provided, either curses or one of the other ones?
Again, it's running in screen so I don't even have it open on any windows.
Of course, that doesn't mean this is the best route to go, but it's been
working for me for so far - I am new to it though. It's a nice pretty
colored interface too :)
Tim
next prev parent reply other threads:[~2009-07-14 15:00 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 [this message]
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
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=20090714150034.GA393@d228.scdc1.swarthmore.edu \
--to=lists+sup@protozoic.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