Gnus development mailing list
 help / color / mirror / Atom feed
From: "Rupert Swarbrick" <rswarbrick@googlemail.com>
To: ding@gnus.org
Subject: Re: nnimap agent caching
Date: Thu, 10 Jul 2008 13:25:23 +0100	[thread overview]
Message-ID: <c9d0f690807100525o4920e2eh78d601574951073a@mail.gmail.com> (raw)
In-Reply-To: <87d4lmg7ea.fsf@dod.no>

> Thanx!  Exactly what I was looking for!
>
> Er... nobody will probably believe it, but I've searched the
> Gnus manual for exactly this information.  I've used `i' and `s'.
>
> What I've _not_ done is, of course, to read the manual linearily.
>
> I almost never do that.  I'm too impatient, I'm afraid.
>

I'm not a gnus developer, but it would be great if you could post some
of what you tried searching for with 's' when you didn't find the
relevant information. It seems to me that if there is some "keyword"
that one naturally thinks of when after a feature, it is useful if it
appears in the documentation near the description of that feature.
Whether or not it's the "correct terminology" as used in the project.

Given the somewhat high technological "barrier to entry" for gnus use,
I suspect that most gnus users are used to skimming manuals. Thus I
suspect that there aren't many users who actually read the manual
through and through until after they've used gnus for some time.

These users are worth pleasing I think if there relevant buzzwords
that can be incorporated in a sensible manner into the manual near the
right location.

That said, I really, like really, like the style of the manual - I
really did grin/laugh quite a few times when I first went through it.
That's something we should be careful not to lose.

Rupert

PS Yeah, I know the mua's gmail. I'm at work.



  reply	other threads:[~2008-07-10 12:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03 19:21 Steinar Bang
2008-07-03 19:27 ` Steinar Bang
2008-07-04  2:33 ` William Xu
2008-07-09 19:54   ` Steinar Bang
2008-07-10 12:25     ` Rupert Swarbrick [this message]
2008-07-10 16:47       ` Steinar Bang

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=c9d0f690807100525o4920e2eh78d601574951073a@mail.gmail.com \
    --to=rswarbrick@googlemail.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).