Gnus development mailing list
 help / color / mirror / Atom feed
From: David Z Maze <dmaze@MIT.EDU>
Subject: Re: How do you read mails when gnus is not available?
Date: Tue, 22 Jul 2003 11:46:37 -0400	[thread overview]
Message-ID: <y68he5ea7j6.fsf@multics.mit.edu> (raw)
In-Reply-To: <microsoft-free.3owueffb0s.fsf@ournature.org> (Jinhyok Heo's message of "Sat, 19 Jul 2003 12:30:59 +0900")

Jinhyok Heo <novembre+dated+1059016389.f4e7aa@ournature.org> writes:

> Well, I want to know how you send and receive mails when your guns is
> not available?

If you're in a situation where you can read mail via IMAP and make
arbitrary outgoing SMTP connections, any other mail reader is fine.  I
tend to use mutt (with vi as an editor) when I'm not willing to wait
for Gnus to start up or dig through my mail.  (And before I figured
out that mutt in fact required far less configuration than Gnus, I was
using pine in the same way.)

> Gnus is something that I cannot do without. But sometimes I am away
> From my machine and it is hard to get good connection to my machine.
> It is quite difficult to do something with a remote gnus due to the
> slow connection.

What problems do you have?  How I use Gnus depends on what sort of
network I have:

-- Excellent (Ethernet to the file servers): run Gnus locally, read
   mail via nnml from networked filesystem (AFS)

-- Good (cable modem): run Gnus remotely with X forwarding

-- Bad (dialup, congested net): run Gnus remotely in text mode in
   screen

I do recommend using screen(1) if you're going to run Emacs in text
mode in a slow environment.  That way if you lose your connection you
haven't lost Emacs, you just need to reconnect to the dormant screen
session.  I do recommend changing the default command key binding,
though, since screen's default (C-a) is also the Emacs start-of-line
character; I use C-].

{14} dmaze% cat .screenrc
startup_message off
escape ^]a

-- 
David Maze             dmaze@mit.edu          http://www.mit.edu/~dmaze/
"Theoretical politics is interesting.  Politicking should be illegal."
	-- Abra Mitchell




  parent reply	other threads:[~2003-07-22 15:46 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
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 [this message]
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=y68he5ea7j6.fsf@multics.mit.edu \
    --to=dmaze@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;
as well as URLs for NNTP newsgroup(s).