From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Proposed new introductory section to the Gnus manual
Date: Mon, 16 Sep 2019 10:55:31 +0800 [thread overview]
Message-ID: <87tv9ddk64.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <s6jblvojbpv.fsf@bobnewell.net>
Bob Newell <bobnewell@bobnewell.net> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>> A hindrance for users at any age :) There are whole aspects of Gnus
>> (scoring, spam, agent categories, etc) that I have never touched,
>> simply
>> because I couldn't be bothered with the learning curve.
>
> As an old retiree myself --- even with 10 years experience with
> Gnus-- there are aspects that I too haven't explored, scoring
> being the most prominent among them.
>
> And yet my gnus startup file is over 1000 lines of elisp (maybe
> half of it comment lines, but still) ... but that does
> underscore the point that without at least some ability with
> elisp, using gnus is probably not feasible.
>
> There might be a way to change that, but would a 'generic' gnus
> miss the point? We use gnus because it's amazing and does crazy
> stuff ... what other client would allow me (just as one small example)
> to set my input method to French, German, or Hawaiian depending
> on the addressee, let alone choose my smtp server based on a
> similar criterion? (Certain people ALWAYS get email from my
> preciously preserved AOL address!)
>
> The limitations of non-programmable clients show themselves
> quickly. Even the more 'advanced' ones fall far short.
Oh I definitely agree, and have no intention of reducing Gnus'
user-facing complexity. But I think a bit more hand-holding for newbies
couldn't hurt. It was truly frustrating in the beginning.
next prev parent reply other threads:[~2019-09-16 2:55 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-18 23:26 Eric Abrahamsen
2019-08-19 0:34 ` dick.r.chiang
2019-08-19 1:06 ` Eric Abrahamsen
2019-08-19 2:46 ` Bob Newell
2019-08-19 7:01 ` Eric S Fraga
2019-08-20 4:26 ` Eric Abrahamsen
2019-08-20 11:37 ` dick
2019-09-09 8:13 ` Eric Abrahamsen
2019-09-09 11:52 ` dick
2019-09-09 18:39 ` Bob Newell
2019-09-09 19:48 ` dick
2019-09-10 2:36 ` Eric Abrahamsen
2019-09-10 20:21 ` dick
2019-09-10 23:50 ` Eric Abrahamsen
2019-09-12 19:19 ` Michael
2019-09-13 9:19 ` Eric Abrahamsen
2019-09-13 15:08 ` Eric S Fraga
2019-09-13 16:54 ` Michael
2019-09-16 2:51 ` Eric Abrahamsen
2019-09-13 18:24 ` Bob Newell
2019-09-13 18:39 ` Change input method or smtp server depending on addressee (was: Proposed new introductory section to the Gnus manual) Jorge A. Alfaro-Murillo
2019-09-14 17:38 ` Change input method or smtp server depending on addressee Štěpán Němec
2019-09-16 18:26 ` Bob Newell
2019-09-16 8:52 ` Robert Pluim
2019-12-20 12:54 ` 황병희
2019-09-16 2:55 ` Eric Abrahamsen [this message]
2019-09-16 18:34 ` Proposed new introductory section to the Gnus manual Bob Newell
2019-09-10 20:39 ` Adam Sjøgren
2019-09-10 20:54 ` dick
2019-09-12 5:31 ` Steinar Bang
2019-09-07 19:50 ` Adam Sjøgren
2019-09-08 17:00 ` Bob Newell
2019-08-19 16:01 ` Adam Sjøgren
2019-08-19 18:04 ` Bob Newell
2019-08-19 18:09 ` Adam Sjøgren
2019-08-20 4:29 ` Eric Abrahamsen
2019-09-07 19:44 ` Adam Sjøgren
2019-08-19 16:16 ` Eric S Fraga
2019-08-20 7:08 ` Bjørn Mork
2019-08-20 9:51 ` Eric S Fraga
2019-08-20 10:32 ` Bjørn Mork
2019-08-20 10:55 ` Eric S Fraga
2019-08-19 17:55 ` Adam Sjøgren
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=87tv9ddk64.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.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 NNTP newsgroup(s).