From: Michael <beriah@opensuse.us>
To: ding@gnus.org
Subject: Re: Proposed new introductory section to the Gnus manual
Date: Fri, 13 Sep 2019 08:54:32 -0800 [thread overview]
Message-ID: <709dc4a4-e915-09cc-0fc2-6aea44b3e082@opensuse.us> (raw)
In-Reply-To: <87d0g4k0z5.fsf@ericabrahamsen.net>
On 9/13/19 1:19 AM, Eric Abrahamsen wrote:
> Michael <beriah@opensuse.us> writes:
>
>> On 9/10/19 3:50 PM, Eric Abrahamsen wrote:
>>> dick <dick.r.chiang@gmail.com> writes:
>>>
>>>> EA> Gnus has a lot of variables with
>>>> EA> pretty convoluted value-structures. I wonder if its Customize support is
>>>> EA> currently up to snuff
>>>>
>>>> It is not. One such convoluted value-structure is `gnus-parameters`.
>>>> Configuring that via the Customize interface is like digging a ditch with a
>>>> toy shovel. Even a basic parameter like `gnus-secondary-select-methods`
>>>> requires knowledge of how a Gnus METHOD is composed.
>>> Yeah, I suppose. Customize just wasn't meant to handle values that
>>> complicated. Gnus also has its own home-grown (of course) "edit forms"
>>> (gnus-eform.el) which currently just dump you in an elisp buffer where
>>> you have to edit elisp forms, but could be smarter about
>>> presenting/parsing complicated values in a user-friendly way.
>>>
>>>> It bears repeating that introducing `gnus-secondary-select-methods` instead of
>>>> vectorizing `gnus-select-method` was a mistake that can still be
>>>> corrected fairly easily.
>>> That's on my list of things to do, but as a user-facing change, it's at
>>> the bottom of the list.
>>>
>>>
>> I really like Gnus and I have tried to use it a couple of times, but
>> always gave up. It is getting harder for me, at my age, to
>> remember/memorize all the different commands.
> 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.
>
>> Not knowing lisp is for me also a hindrance.
>>
>> However, I want to thank you for working on the introduction and the
>> quick guide. It has given me a better understanding. With that, and
>> the added links posted, I'm getting more familiar with how to use Gnus
>> and close to using it for all my news and email :)
>>
>> I'd love to help since I'm just an old retired man, but don't know
>> enough to help :)
> With all due respect, your ignorance of Gnus might be just the thing we
> need :) I think most people on this list remember that the early
> experience was bad, but don't really remember the details, or what would
> have helped. If you kept an eye on discussion here, and piped up
> whenever a bit of information seemed a) nonsensical or b) just the thing
> you needed to figure out a problem, that might be the biggest help you
> could provide.
>
> For instance, what part of my intro (and the other links posted in this
> thread) was most useful?
>
> Thanks!
> Eric
>
>
Ok, here are some thoughts while reading the intro and comments:
I actually laughed, and liked, the "DON"T PANIC", but how about adding
one sentence with something like, "Here is some brief help to get you
started using Gnus". Something brief and easy, before delving into the
origin of Gnus?
"tick" is mentioned a couple of times, but what is a "tick"? At this
point, would a more generic term suffice, such as "mark" or "flag" since
this is the intro?
I like the improvement comments that others have mentioned and that you
have agreed with, so no need to add anything to them :)
I am very glad for the part mentioning what to type when Gnus has
started. I do have a "code" comment/question about this. When I start
Gnus, I see the menu bar and Gnus mascot/icon/whatever it's called. So,
how about a line under the menu showing different keyboard keys to type,
such as "q", "L", "AA", "r or R", "f" and what each means? It could be a
line that could be removed via customization when the experienced user
didn't need it there?
A number of times when I would start, I couldn't figure out how to get
out of where I was at to get back to beginning screen (or wherever). So,
I would just just quit gnus/emacs and wait some time before trying
again. A line similar to above might help newbies when first starting
if/when they start and get confused and don't know what to do :)
Ok I'll quit for now.
Thanks for allowing my input.
next prev parent reply other threads:[~2019-09-13 16:54 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 [this message]
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=709dc4a4-e915-09cc-0fc2-6aea44b3e082@opensuse.us \
--to=beriah@opensuse.us \
--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).