From: Don Saklad <dsaklad@nestle.ai.mit.edu>
Subject: 5, 10, 20 years from now
Date: 23 Apr 2003 08:41:17 -0400 [thread overview]
Message-ID: <y44k7dlfksy.fsf@nestle.ai.mit.edu> (raw)
Questions asked by really big fans of gnus mail...
a. 5, 10 or 20 years from now, do you guys think that gnus mail will
set itself up automatically without any knowledge needed on the
part of neophytes?...
b. Possibly, how could this be solved so that the dot file will set up
automatically according to the parameters of the system setup of
the end user?...
c. What delays this being done now or relatively soon?...
In the future when we'll have real computers we won't be required to
have arcance knowledge to operate them to their greatest capacity!
Weblog
http://zork.net/~dsaklad/gnusmail.html
next reply other threads:[~2003-04-23 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 12:41 Don Saklad [this message]
[not found] ` <m3u1cp1hr5.fsf@quimbies.gnus.org>
2003-04-24 4:50 ` Jason Earl
2003-04-24 23:05 ` David Masterson
2003-04-26 4:11 ` Richard Hoskins
2003-04-25 14:38 ` Paolo Amoroso
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=y44k7dlfksy.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).