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:51:43 +0800 [thread overview]
Message-ID: <87y2ypdkcg.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <709dc4a4-e915-09cc-0fc2-6aea44b3e082@opensuse.us>
Michael <beriah@opensuse.us> writes:
[...]
>> 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?
The Info format allows for subheadings, so this could be something like
"Don't Panic:\tYour First Twenty Minutes With Gnus" or something like that.
> "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 agree "flag" is likely to be more generally understood.
> 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 :)
A sort of "quick keys" popup sounds like a great idea. Gnus already
provides a "H" keymap prefix for help-related things, so "H h" could
always pop up the quick keys tips.
Then we could have a customization option to always display the popup.
[btw, "q" is almost always the key you want to "back out of" wherever
you've gotten. This is what I meant by "vim-style tutorial": the most
important information is always how to quit!]
> Thanks for allowing my input.
All input is allowed, but not all input is processed :)
next prev parent reply other threads:[~2019-09-16 2:51 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 [this message]
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=87y2ypdkcg.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).