unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Joel Reicher <joel.reicher@gmail.com>
To: divya@subvertising.org
Cc: help-gnu-emacs@gnu.org
Subject: Re: E-mail package
Date: Sat, 28 Dec 2024 18:13:04 +1100	[thread overview]
Message-ID: <86jzbk9t6n.fsf@gmail.com> (raw)
In-Reply-To: <e43e934980c0044168f9de6915b03674@subvertising.org> (divya@subvertising.org's message of "Sat, 28 Dec 2024 03:38:59 +0000")

divya@subvertising.org writes:

>> If you have not already, then you might want to skim through 
>> the chapter of Emacs built-in email client, RMAIL.  It is 
>> included in the Emacs user manual and can be read by evaluating 
>> the following expression in Emacs:
>>    (info "(emacs) Rmail")
>> Or, type C-h r to begin reading the Emacs user manual, and then 
>> type ‘g’ to display the "Go to node: " prompt, and then type 
>> rmail and press the Return/Enter key.  The Labels, Attrs, and 
>> Summary sections might describe a solution that you could use.
>
> I've always wondered how Gnus differs from Rmail, if one were to 
> use the latter over the former what advantages would one have, 
> and what can one might miss?

In my opinion the biggest difference is the mail storage 
support. AFAIK Rmail really only has one type: its own files. It 
depends on external programs to move or copy messages across from 
other types, both local and remote.

Gnus even just for mail is quite different on that front: (info 
"(gnus) Mail Source Specifiers").

But  Gnus also (mostly) unifies the news and mail reading 
experience, treating news as just another kind of message storage.

Regards,

        - Joel



  parent reply	other threads:[~2024-12-28  7:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-23 17:27 E-mail package Christopher Howard
2024-12-23 18:50 ` gfp
2024-12-24 16:48   ` Christopher Howard
2024-12-25  9:22     ` gfp
2024-12-26  6:27       ` Joel Reicher
2024-12-26 20:37         ` gfp
2024-12-26 21:39           ` tpeplt
2024-12-28  3:38             ` divya
2024-12-28  4:10               ` Bob Newell
2024-12-28  7:13               ` Joel Reicher [this message]
2024-12-28 17:39               ` tpeplt
2024-12-28 18:13                 ` Jean Louis
2024-12-26 16:28       ` Christopher Howard
2024-12-27 15:47         ` Eric S Fraga
2024-12-27 15:45       ` Eric S Fraga
  -- strict thread matches above, loose matches on Subject: below --
2024-10-19 14:15 gfp
2024-10-19 15:21 ` Jude DaShiell
2024-10-20  3:19 ` W. Greenhouse
2024-10-21  8:47   ` Eric S Fraga
2024-12-06 22:11 ` Jean Louis
2024-12-21 11:50 ` Joel Reicher

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=86jzbk9t6n.fsf@gmail.com \
    --to=joel.reicher@gmail.com \
    --cc=divya@subvertising.org \
    --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).