From: Tommy Kelly <tommy.kelly@verilab.com>
To: info-gnus-english@gnu.org
Cc: ding@gnus.org
Subject: Re: Error in (info "(gnus)Splitting Mail")
Date: Sun, 19 Dec 2010 09:53:14 -0600 [thread overview]
Message-ID: <m2pqsxwyhh.fsf@verilab.com> (raw)
In-Reply-To: <874oa9u9au.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Sat, 18 Dec 2010 16:33:47 -0600 Tommy Kelly <tommy.kelly@verilab.com> wrote:
>
> TK> The person who wrote the stuff, understands it in intense
> TK> detail without the documentation, and therefore has little or no need
> TK> of the documentation thinks the documentation is more readable as it is.
>
> TK> The person who is trying to learn the stuff, and must rely heavily on
> TK> said documentation thinks the documentation would be more readable with a
> TK> a minor fix.
>
> Štěpán was noting a minor issue: if mail comes from majordomoXcom (any
> single character) instead of majordomo.com, it will match that splitting
> rule. I don't think Štěpán suggested it would make the documentation
> more readable to fix that.
You're right. Štěpán explained the thing to me and then flagged it to
The Documenters. *I* am suggesting that Štěpán's flagging was useful and
that, contrary to Lars's view, the proposed fix is worthwhile and makes
things more readable[1].
And my underlying point was that while Lars is an undoubted expert in
Gnus, *I* am an expert in being a new and clueless user of it. The
documentation has an intended core audience, and it ain't Lars.
So Štěpán's point was one of regexp structure; mine, one of pedagogy.
All that said. I'm new here and have invested a mere fraction of the
hours in this project that y'all have. So don't hesitate to pat me on
the head and say "Shhhh! The grown-ups are speaking." :-)
Tommy
[1] Or rather, it makes it more consistent and understandable --
a.k.a. better. I'm with everyone else in that adding toothpicks rarely
makes for improved *read*-ability. But that -- toothpicks (and (to
further make the (undoubtedly made (albeit obliquely) by now) point)
parens) -- is the life we have chosen for ourselves.
next prev parent reply other threads:[~2010-12-19 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5.1292548275.31723.info-gnus-english@gnu.org>
[not found] ` <87fwtwzqm5.fsf@topper.koldfront.dk>
[not found] ` <m2r5dg3086.fsf@verilab.com>
[not found] ` <87aak4488w.fsf_-_@gmail.com>
[not found] ` <m2d3p02fd2.fsf@verilab.com>
2010-12-18 8:16 ` Štěpán Němec
[not found] ` <mailman.13.1292660334.28168.info-gnus-english@gnu.org>
2010-12-18 18:45 ` Lars Magne Ingebrigtsen
2010-12-18 22:33 ` Tommy Kelly
2010-12-19 14:27 ` Ted Zlatanov
2010-12-19 15:24 ` Štěpán Němec
2010-12-19 15:53 ` Tommy Kelly [this message]
2010-12-27 15:07 ` Ted Zlatanov
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=m2pqsxwyhh.fsf@verilab.com \
--to=tommy.kelly@verilab.com \
--cc=ding@gnus.org \
--cc=info-gnus-english@gnu.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).