From: michael+sup@stapelberg.de (Michael Stapelberg)
Subject: [sup-talk] Using sup on multiple computers?
Date: Fri, 10 Jul 2009 12:59:42 +0200 [thread overview]
Message-ID: <1247223427-sup-4016@x200> (raw)
In-Reply-To: <1247194599-sup-5843@javelin>
Hi,
Excerpts from Edward Z. Yang's message of Fr Jul 10 04:57:14 +0200 2009:
> 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.
I?ve been using mutt like this for about a year or so but I generally
don?t want to continue with this approach. It has the disadvantage of
having the need to copy attachments to your computer before being able
to display them (think of PDFs) and of not scaling well when on a slow
internet connection (IMAP traffic is less than a whole user interface).
Best regards,
Michael
next prev parent reply other threads:[~2009-07-10 10:59 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
2009-07-10 10:59 ` Michael Stapelberg [this message]
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=1247223427-sup-4016@x200 \
--to=michael+sup@stapelberg.de \
/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