From: Joseph Barillari <jbarilla@princeton.edu>
Cc: ding@gnus.org
Subject: Re: How do you read mails when gnus is not available?
Date: Mon, 21 Jul 2003 23:49:03 -0400 [thread overview]
Message-ID: <87ispv6x1s.fsf@bigbox.barillari.org> (raw)
In-Reply-To: <microsoft-free.3owueffb0s.fsf@ournature.org> (Jinhyok Heo's message of "Sat, 19 Jul 2003 12:30:59 +0900")
>>>>> "JH" == Jinhyok Heo <novembre+dated+1059016389.f4e7aa@ournature.org> writes:
JH> Well, I want to know how you send and receive mails when your
JH> guns is not available?
JH> Gnus is something that I cannot do without. But sometimes I am
JH> away from my machine and it is hard to get good connection to
JH> my machine. It is quite difficult to do something with a
JH> remote gnus due to the slow connection.
JH> How do you manage this kind of situation? I wish to compare
JH> various ways to enjoy email without gnus.
When you say 'remote emacs', are you referring to an X session, or a
terminal session?
If you're referring to the latter, short of switching back to BSD
mail(1), I doubt you can get that much speed improvement.
If you just want to try a different terminal-based client (which won't
be much better than terminal-based emacs in terms of
bytes-over-the-wire), I recommend mutt. I used to use it before I
switched to Gnus. It's a full-featured, quick curses-based
client. Only downside to it is that you have to boot up emacs every
time you change a message. (Admittedly, it's possible to avoid this,
either by using vi, or by pulling some tricks with ansi-term and
emacsserver.)
Best, --Joe
--
Joseph Barillari -- http://barillari.org
next prev parent reply other threads:[~2003-07-22 3:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-19 3:30 Jinhyok Heo
2003-07-22 3:49 ` Joseph Barillari [this message]
2003-07-22 8:34 ` Kai Großjohann
2003-07-23 5:56 ` Xavier Maillard
2003-07-23 21:29 ` D. Michael McFarland
2003-07-24 1:19 ` Jinhyok Heo
2003-07-24 8:10 ` Juha Autero
[not found] ` <hhznj3wvv6.fsf@blah.pl>
2003-07-24 20:18 ` Jesper Harder
2003-07-24 21:47 ` Xavier Maillard
2003-07-24 22:32 ` Joseph Barillari
2003-07-26 18:30 ` Carsten Thönges
2003-07-27 0:19 ` Joseph Barillari
2003-07-24 11:16 ` Malcolm Purvis
2003-07-24 21:48 ` Xavier Maillard
2003-07-26 9:32 ` Kai Großjohann
2003-07-26 10:02 ` Matthias Andree
2003-07-29 5:47 ` Xavier Maillard
2003-07-22 15:46 ` David Z Maze
2003-07-22 16:06 ` Jody Klymak
2003-07-23 6:09 ` Xavier Maillard
2003-07-21 23:44 Jinhyok Heo
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=87ispv6x1s.fsf@bigbox.barillari.org \
--to=jbarilla@princeton.edu \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).