Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: ezyang@MIT.EDU (Edward Z. Yang)
Subject: [sup-talk] Using sup on multiple computers?
Date: Thu, 09 Jul 2009 22:57:14 -0400	[thread overview]
Message-ID: <1247194599-sup-5843@javelin> (raw)
In-Reply-To: <1247186181-sup-1712@x200>

Excerpts from Michael Stapelberg's message of Thu Jul 09 20:38:25 -0400 2009:
> I?d like to use sup on my notebook and on my workstation. Is there any
> simple/recommended way to synchronize the index? I figured using multiple
> clients in parallel is one of the big advantages of IMAP and I?d love to keep
> it that way while using sup.

The easiest way is to not; since Sup is a command line application, it's trivial
to spin it up on a server you have access to and simply SSH in to check your
mail.

Cheers,
Edward


  reply	other threads:[~2009-07-10  2:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-10  0:38 Michael Stapelberg
2009-07-10  2:57 ` Edward Z. Yang [this message]
2009-07-10 10:59   ` Michael Stapelberg
2009-07-10  3:03 ` Jonathan Lassoff
2009-07-10 14:30   ` Andrei Thorp
2009-07-14 15:43 ` John Bent
2009-07-14 19:33   ` Ben Walton
2009-07-14 19:35   ` Michael Stapelberg

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=1247194599-sup-5843@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