unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: floyd@apaflo.com (Floyd L. Davidson)
To: help-gnu-emacs@gnu.org
Subject: Re: Reading/Managing mail with emacs
Date: Sat, 06 Oct 2007 01:30:17 -0800	[thread overview]
Message-ID: <878x6gvbdi.fld@apaflo.com> (raw)
In-Reply-To: mailman.1759.1191660010.18990.help-gnu-emacs@gnu.org

Andrew Walrond <andrew@walrond.org> wrote:
>So, a quick google reveals VM as the front runner for email. Am I right?
>Any gotchas or missing features to be aware of?

GNUS is the heavy weight champ.

A few hints at what can be done...  my ~/.gnus.el file
is 58k bytes.  I'm not really any great shakes at
hacking elisp either; but over the years things get
added here and there. :-)

The one "problem" with running gnus is that it
necessarily creates a large number of buffers,
customizes menus, etc etc; and basically takes over
Emacs.  If you run Emacs as an edit server (highly
recommended), it works much better to invoke an Emacs
process separately from that server to run gnus for
Usenet and email.

I read Usenet and email all as one application.  Email
"groups" appear to just be added newsgroups.  (A
separate process actually fetches the mail; hence, when
newgroups get updated, new email is also transfered to
control of gnus.)

It works very nicely that way, and eventually you might
get around to such things as customized keybindings,
filters, and who knows what.  The initial configuration
is not simple though!  For example, you would probably
want each mailing list to be seen as a distinct
"newsgroup", and you might want you outgoing mail to
those groups archived separately.  You also might want
distinct headers and/or signature lines for each group.
That's just for starters...

Look for example configurations on the net, and check
out gnu.emacs.gnus.

-- 
Floyd L. Davidson <http://www.apaflo.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska)              floyd@apaflo.com

       reply	other threads:[~2007-10-06  9:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1759.1191660010.18990.help-gnu-emacs@gnu.org>
2007-10-06  9:30 ` Floyd L. Davidson [this message]
2007-10-06 11:56   ` Reading/Managing mail with emacs Reiner Steib
2007-10-07  5:20 ` Tim X
2007-10-07 18:04   ` Sivaram Neelakantan
     [not found]   ` <mailman.1837.1191860565.18990.help-gnu-emacs@gnu.org>
2007-10-08 16:38     ` Joel J. Adamson
2007-10-06  8:43 Andrew Walrond
2007-10-06  8:48 ` Leo
2007-10-06  9:39   ` Alexey Pustyntsev
2007-10-06  9:50 ` Daniel Pittman
2007-10-06 13:11   ` Andreas Eder
2007-10-10  7:23   ` Dmitri Minaev
2007-10-10 10:56     ` Daniel Pittman
2007-10-15  9:02       ` Dmitri Minaev
2007-10-08 19:21 ` Sven Bretfeld
     [not found] ` <mailman.1846.1191871309.18990.help-gnu-emacs@gnu.org>
2007-10-09 13:57   ` Joel J. Adamson
2007-10-09 14:50     ` CHENG Gao
     [not found]     ` <mailman.1883.1191941777.18990.help-gnu-emacs@gnu.org>
2007-10-09 16:18       ` Joel J. Adamson
2007-10-10  1:54     ` Tim X

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878x6gvbdi.fld@apaflo.com \
    --to=floyd@apaflo.com \
    --cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).