From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: How to set up gnus email for novices with little mastery.
Date: Wed, 29 Sep 2004 11:47:37 -0400 [thread overview]
Message-ID: <4n8yataxgm.fsf@lifelogs.com> (raw)
In-Reply-To: <y448yat883s.fsf@nestle.csail.mit.edu>
On 29 Sep 2004, dsaklad@nestle.csail.mit.edu wrote:
> How do you figure out backend neither having any experience in
> thinking about it nor even knowing the significance of backend ?...
>
> Backend appears too complicated a thing for many people with no
> mastery or it would require dedicated study, too steep a learning
> curve of more than a mere few moments.
Backends are explained in the Gnus manual. Reading the manual is a
requirement for using Gnus, you can't just expect it to "work" (there
are other news readers that do that).
Gnus will have setup assistants one day. It doesn't now, so setup is
a manual chore. If you or anyone else would like to work on the setup
assistants, that would help - they are at the embryo stage now.
Ted
next prev parent reply other threads:[~2004-09-29 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 12:35 Don Saklad
[not found] ` <m28yat2mw4.fsf@Stella-Blue.local>
[not found] ` <y448yat883s.fsf@nestle.csail.mit.edu>
2004-09-29 15:47 ` Ted Zlatanov [this message]
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=4n8yataxgm.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
/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).