From: Don Saklad <dsaklad@nestle.ai.mit.edu>
Subject: Re: Automated gnus email setup for people already using gnus.
Date: 19 Dec 2002 17:40:12 -0500 [thread overview]
Message-ID: <y4465tpeipf.fsf@nestle.ai.mit.edu> (raw)
In-Reply-To: <y44hedcopy2.fsf@nestle.ai.mit.edu>
> Once you've got gnus, would there be a way of setting up gnus email with
> something that automatically analyzes your set up on your system, goes
> ahead and makes the dot file and you're ready with no other effort
> usually?...
>
> Could this be developed for neophyte types?...
>
> It picks one configuration for you to begin using gnus email.
>
> It also offers for those who're not neophytes, those more in the know,
> options to further optimize the beginner configuration.
>
> So, in gnus you run a command and it sets up or runs a check on a set
> up for gnus email. Afterward, you're ready to go with no necessary
> tweaking usually.
Yes, this could be done. The difficulties with setting up Gnus are due to
programmers' failure to grasp that a broken user interface is just an
example of broken ordinary code. No competent programmer would code C or
Basic or Lisp subroutines with such crazy lambda lists as the Gnus set-up
procedure has.
oo--ONR
next parent reply other threads:[~2002-12-19 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <y44hedcopy2.fsf@nestle.ai.mit.edu>
2002-12-19 22:40 ` Don Saklad [this message]
2002-12-24 5:52 ` Jonathon Isaac Swiderski
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=y4465tpeipf.fsf@nestle.ai.mit.edu \
--to=dsaklad@nestle.ai.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).