Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Don Saklad <dsaklad@nestle.csail.mit.edu>
Subject: How to set up gnus email for novices with little mastery.
Date: 29 Sep 2004 08:35:18 -0400	[thread overview]
Message-ID: <y44zn39s16h.fsf@nestle.csail.mit.edu> (raw)

A relative novice using emacs rmail does not have enough mastery to
set up the dotfile for gnus email nor to do whatever other
accompanying tasks to get gnus email up and running. What hints, tips
and pointers are there for such users interested in trying gnus email
that do not require more than a few moments of study through a steep
that learning curve so perceived ?...

The existing instructive informational links and newsgroups do assume
a relatively advanced or intermediate level of user.


             reply	other threads:[~2004-09-29 12:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-29 12:35 Don Saklad [this message]
     [not found] ` <m28yat2mw4.fsf@Stella-Blue.local>
     [not found]   ` <y448yat883s.fsf@nestle.csail.mit.edu>
2004-09-29 15:47     ` Ted Zlatanov
2004-09-29 16:08     ` Tim McNamara
     [not found]       ` <4nmzz99f3i.fsf@lifelogs.com>
     [not found]         ` <m2oejosycp.fsf@Stella-Blue.local>
     [not found]           ` <4nwtybpyxe.fsf@lifelogs.com>
     [not found]             ` <m31xgjhh51.fsf@localhost.localdomain>
2004-10-01  8:35               ` Don Saklad
2004-10-04  8:31 Don Saklad
     [not found] ` <y44pt3yev4y.fsf@nestle.csail.mit.edu>
     [not found]   ` <y68llemh8fp.fsf@contents-vnder-pressvre.mit.edu>
     [not found]     ` <5i7jq6cpku.fsf@fencepost.gnu.org>
2004-10-05  0:34       ` Tim McNamara
     [not found]       ` <878yam5n9v.fsf@koldfront.dk>
2004-10-05  1:00         ` Dan Muller
     [not found]           ` <m2vfdpua7e.fsf@Stella-Blue.local>
2004-10-05  3:50             ` Dan Muller

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=y44zn39s16h.fsf@nestle.csail.mit.edu \
    --to=dsaklad@nestle.csail.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).