Gnus development mailing list
 help / color / mirror / Atom feed
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: Sat, 18 Dec 2010 16:33:47 -0600	[thread overview]
Message-ID: <m2aak290dw.fsf@verilab.com> (raw)
In-Reply-To: <m3r5deudhi.fsf@quimbies.gnus.org>

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Štěpán Němec <stepnem@gmail.com> writes:
>
>>>      ("list.\\1" "From:.* \\(.*\\)-list@majordomo.com")
>>>
>>> So shouldn't the dot after "majordomo" be double escaped?
>>
>> Yeah, that's obviously just an error in the documentation, but a mostly
>> harmless one, as "." matches the dot anyway...
>
> It's more readable without the \\, and the chance for false positives is
> minuscule, so I think I'll just leave it as is.

So: 

The person who wrote the stuff, understands it in intense
detail without the documentation, and therefore has little or no need
of the documentation thinks the documentation is more readable as it is.

The person who is trying to learn the stuff, and must rely heavily on
said documentation thinks the documentation would be more readable with a
a minor fix.

Hmmm.

:-)

Tommy

  reply	other threads:[~2010-12-18 22:33 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 [this message]
2010-12-19 14:27               ` Ted Zlatanov
2010-12-19 15:24                 ` Štěpán Němec
2010-12-19 15:53                 ` Tommy Kelly
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=m2aak290dw.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).