From: dick <dick.r.chiang@gmail.com>
To: ding@gnus.org
Subject: Re: Proposed new introductory section to the Gnus manual
Date: Mon, 09 Sep 2019 15:48:16 -0400 [thread overview]
Message-ID: <875zm1w8sf.fsf@gmail.com> (raw)
In-Reply-To: <87tv9lmhzt.fsf@bobnewell.net>
BN> I suppose YMMV but I found it very useful
The hard part is not the quirky UX which he calls the "essential 5%". The
hard part is configuring Gnus to something usable, and that is completely
glossed over.
I'm typical of most newcomers who merely want their cloud service, i.e.,
Gmail, integrated into emacs. I couldn't find anything authoritative for this
pedestrian task. I found nnimap without dovecot unusable. And I am wary of
nnmaildir because I hesitate to do my own search indexing.
BN> gnus is niche software.
It shouldn't be for two reasons:
1) As the built-in client, it needs to work out of the box. Alas, it's not
meeting the duties of the throne. Its recalcitrance towards new users is like
Yahoo occupying Firefox's default search engine when Google is clearly superior.
2) It's awesome. While integration with emacs alone is worth the price of
admission, Gnus bests other mua's because its message queue paradigm subsumes
all my news, mail, and reddit activity in a single dashboard. As it stands,
you *must* know elisp to be a day-to-day Gnus user, and I'm looking to change
that.
next prev parent reply other threads:[~2019-09-09 19:48 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 [this message]
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 ` Proposed new introductory section to the Gnus manual Eric Abrahamsen
2019-09-16 18:34 ` 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=875zm1w8sf.fsf@gmail.com \
--to=dick.r.chiang@gmail.com \
--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).