From: William Baxter <web-sup@superscript.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Fwd: Automatic labels backup
Date: Sat, 19 Dec 2009 18:57:24 -0500 [thread overview]
Message-ID: <1261265869-sup-7604@kronos> (raw)
In-Reply-To: <1260855317-sup-863@ezyang>
Excerpts from Edward Z. Yang's message of Tue Dec 15 00:35:42 -0500 2009:
> Ever had your index corrupted, and your last backup of your labels from
> a month ago? Ever had to go speed through a month's worth of mail?
>
> Well, now, you can /not/ have to do that, with a handy-dandy automated
> index dump tool that I've written. It's at the bottom of the
> hooks page here: <http://sup.rubyforge.org/wiki/wiki.pl?Hooks> and I've
> reproduced it below for completeness.
For a few weeks I have used sup to read the same mail on two hosts: an office
desktop and a laptop. Each host fetches mail from the same IMAP server. I use
the desktop all day, altering labels frequently, and consequently find reading
from the laptop less useful. I want to sync labels across the two hosts.
How much additional work does it take to turn an index dump into a sup-to-sup
sync mechanism? Suppose that on one host you dump the index and send a signed
message. This reaches the receiving host when you read mail there. Use it to
update the index, and the receiving host has labels matching those on the
sending host.
Cheers, W.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-12-20 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 5:35 Edward Z. Yang
2009-12-19 19:02 ` William Morgan
2009-12-19 19:13 ` Edward Z. Yang
2009-12-19 23:57 ` William Baxter [this message]
2009-12-21 16:35 ` William Morgan
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=1261265869-sup-7604@kronos \
--to=web-sup@superscript.com \
--cc=sup-talk@rubyforge.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