From: ezyang@MIT.EDU (Edward Z. Yang)
Subject: [sup-talk] New to Sup and some imap sync questions
Date: Wed, 29 Apr 2009 13:04:40 -0400 [thread overview]
Message-ID: <1241024581-sup-9014@javelin> (raw)
In-Reply-To: <1240940037-sup-2915@bakkdoor-ubuntu>
Excerpts from Christopher Bertels's message of Tue Apr 28 13:49:04 -0400 2009:
> Just wondering if this is ever planned? Since now, even if I have Sup installed
> on my different machines, I still need to sync all the settings when I change
> something (e.g. adding a hook-script or something else). Or is there an easy
> way to sync my Sup settings etc?
Hello Christopher,
My current understanding is that William is not interested in mucking around
with IMAP any more than he has to, so unless someone steps up and submits
some patches there will not be syncing back to IMAP.
As for handling Sup on multiple machines, I think the current best practice
is "don't"; pick one machine, make it ssh'able into, and use that to handle
all of your mail.
Cheers,
Edward
next prev parent reply other threads:[~2009-04-29 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 17:49 Christopher Bertels
2009-04-29 17:04 ` Edward Z. Yang [this message]
2009-04-29 18:09 ` William Morgan
2009-04-29 18:38 ` Edward Z. Yang
2009-04-29 20:16 ` William Morgan
2009-04-29 20:58 ` William Morgan
2009-04-29 20:48 ` Christopher Bertels
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=1241024581-sup-9014@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