From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: Improving the spam.el documentation.
Date: Tue, 08 Jun 2004 11:38:40 +1000 [thread overview]
Message-ID: <87aczeu8v3.fsf@enki.rimspace.net> (raw)
In-Reply-To: <4nr7srpabj.fsf@lifelogs.com>
On 8 Jun 2004, Ted Zlatanov wrote:
> On Mon, 31 May 2004, daniel@rimspace.net wrote:
>
>> -First, some hooks will get installed by @code{spam-initialize}. There
>> +First, some hooks will get installed by @code{spam-initialize}. There
>
> I thought there were always two spaces after a period. Is Texinfo
> different?
Nope. "French" spacing is two space after a period, and that is one of
the two major styles. The other is, of course, a single space after a
period. I can't recall the name now, but can dig it out if you care. :)
Er, it may be that texinfo, or the documentation, has a standard that I
didn't spot, or that was changed when I hit M-q to reformat a paragraph;
my Emacs is set to single-space after sentence mode.
[...]
[...]
>> +@c REVIST: Do we actually need to go into this here? --daniel@rimspace.net
>> +This group name must be @emph{unqualified} name; fancy splitting cannot
>> +send mail to another back-end during the split process, so setting
>> +@code{spam-split-group} to a qualified name will result in that full
>> +string being used as the destination group.
>> +
>> +You can also give @code{spam-split} a parameter, e.g.
>> +@code{spam-use-regex-headers} or @code{"maybe-spam"}. Why is this
>> +useful?
>
> Feel free to move this information, but I think it needs to be stated
> somewhere. The extra parameters to spam-split can make it very
> useful for all kinds of strange setups.
I don't entirely disagree, which is why I left it in place. It just
seemed odd to be giving something of a tutorial on using Gnus splitting
at this point, but obviously it helped someone. :)
> (s/REVIST/REVISIT/)
Er, yes. :)
[...]
> Overall a very nice job, I think it should go into CVS. I'd like one
> other person to review the patch, though, due to its size.
Thanks. I am glad that you think it was worth it. As with anything,
more review is useful - I probably missed a couple of glaring errors
where I saw what I thought, not what I wrote, since it is a big
document. :)
Daniel
--
Good artists copy, great artists steal.
-- Pablo Picasso
next prev parent reply other threads:[~2004-06-08 1:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 13:26 Daniel Pittman
2004-05-28 15:00 ` Jesper Harder
2004-05-28 16:27 ` Ted Zlatanov
2004-05-31 13:34 ` Daniel Pittman
2004-06-07 16:56 ` Ted Zlatanov
2004-06-08 1:29 ` Daniel Pittman
2004-06-08 14:31 ` Ted Zlatanov
2004-06-07 17:06 ` Ted Zlatanov
2004-06-08 1:38 ` Daniel Pittman [this message]
2004-06-08 2:25 ` Jesper Harder
2004-06-08 3:28 ` Daniel Pittman
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=87aczeu8v3.fsf@enki.rimspace.net \
--to=daniel@rimspace.net \
/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).