From: lists+sup@protozoic.com (Tim Gray)
Subject: [sup-talk] problems with Maildir and IMAP offline
Date: Tue, 14 Jul 2009 11:28:06 -0400 [thread overview]
Message-ID: <20090714152806.GC393@d228.scdc1.swarthmore.edu> (raw)
In-Reply-To: <1247584002-sup-504@ntdws12.chass.utoronto.ca>
On Tue 14, Jul'09 at 11:07 AM -0400, Ben Walton wrote:
> It's something I'd like too (not to play nice with other clients, but
> because it's "just better").
This sound like a good thing. In my experience, 'just better' usually
equals 'playing nice', since 'playing nice' usually equals following the
standards. That's how Maildirs are supposed to work - if everybody followed
the spec, we'd be set.
Though I don't program for a living, nor do I know any Ruby, it seems like a
doable thing. Is there something fundamental blocking per-message sync-back
of status as you read/delete/otherwise modify your mail? I would assume
there a reference to the original message location in a message's database
entry. If a message gets read, write an S at the end of the filename and
move it to /cur. If it gets deleted, delete it. Operations on a message
should affect the database and the mail store at the same time. Why is
something like sup-sync-back even necessary?
Anyway, these are just the musings of someone who doesn't have the tools to
write something like sup, so I'll be quiet now before I embarrass myself any
further.
next prev parent reply other threads:[~2009-07-14 15:28 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 [this message]
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=20090714152806.GC393@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