unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs Mini Manual (PART 3) - CUSTOMIZING AND EXTENDING EMACS
Date: Wed, 09 Jul 2014 18:55:17 +0200	[thread overview]
Message-ID: <87lhs2qxoq.fsf@debian.uxu> (raw)
In-Reply-To: mailman.5117.1404898261.1147.help-gnu-emacs@gnu.org

Robert Thorpe <rt@robertthorpeconsulting.com> writes:

> I recommend using a new version of the Emacs manual
> set.  The last version of Emacs 18 was released more
> than 21 years ago.  The current manual describes
> RMAIL in detail.  A separate manual describes GNUS,
> that manual is part of the set.  "Message-mode" is
> the mode for composing email and newsgroup posts that
> comes with GNUS.

So message-mode comes with Gnus? I thought it was older
than Gnus, pre-Internet, pre-everything, perhaps used
with uucp or even for intra-computer "mails". It
doesn't have the "gnus-" prefix that is very
consistently implemented in the Gnus world.

> It's used by GNUS, RMAIL and several other programs.
> It's frequently used, I'm using it now, that's why
> it's included in the manual set.  Of-course reading
> an old manual is still useful, many things haven't
> changed.

Yes.

-- 
underground experts united


       reply	other threads:[~2014-07-09 16:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5117.1404898261.1147.help-gnu-emacs@gnu.org>
2014-07-09 16:55 ` Emanuel Berg [this message]
2014-07-11 11:51   ` Emacs Mini Manual (PART 3) - CUSTOMIZING AND EXTENDING EMACS Robert Thorpe
     [not found] <mailman.5279.1405079523.1147.help-gnu-emacs@gnu.org>
2014-07-11 12:07 ` Emanuel Berg
2014-07-01  4:41 solidius4747
2014-07-01  7:44 ` James Freer
     [not found] ` <mailman.4638.1404200703.1147.help-gnu-emacs@gnu.org>
2014-07-01 14:16   ` Emanuel Berg
2014-07-01 14:38     ` James Freer
     [not found]     ` <mailman.4649.1404225527.1147.help-gnu-emacs@gnu.org>
2014-07-08  8:36       ` solidius4747
2014-07-08 15:09         ` Emanuel Berg
2014-07-08 16:18           ` Drew Adams
2014-07-08 16:45           ` solidius4747
2014-07-08 21:36             ` Emanuel Berg
2014-07-09  2:41               ` solidius4747
2014-07-09  8:52                 ` Robert Thorpe
2014-07-09 17:11                 ` Emanuel Berg
2014-08-25 14:05             ` Jude DaShiell
2014-07-08 18:56           ` Robert Thorpe
     [not found]           ` <mailman.5091.1404836351.1147.help-gnu-emacs@gnu.org>
2014-07-08 21:21             ` Emanuel Berg
2014-07-09  8:44               ` Robert Thorpe
2014-07-10  2:11               ` Bob Proulx
     [not found]               ` <mailman.5163.1404958319.1147.help-gnu-emacs@gnu.org>
2014-07-10 22:16                 ` Emanuel Berg
2014-07-12 14:52                   ` Javier
2014-07-12 19:49                     ` Emanuel Berg
2014-07-12 23:30                       ` Javier
2014-07-13 16:52                         ` Emanuel Berg
2014-07-13  1:40                     ` Robert Thorpe
2014-07-07 23:12 ` Emanuel Berg
2014-07-08  8:37   ` solidius4747
2014-07-08 15:15     ` Emanuel Berg
2014-07-08 16:48       ` solidius4747
2014-07-08 21:43         ` Emanuel Berg

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=87lhs2qxoq.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --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).