Gnus development mailing list
 help / color / mirror / Atom feed
From: Niklas Morberg <niklas.morberg@axis.com>
Subject: [PATCH] spam.el docstring fix (was: Ham messages not being moved anymore)
Date: Tue, 06 May 2003 15:18:18 +0200	[thread overview]
Message-ID: <uy91kz011.fsf_-_@axis.com> (raw)
In-Reply-To: <4ny91sasyn.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Wed, 30 Apr 2003 11:46:40 -0400")

[-- Attachment #1: Type: text/plain, Size: 936 bytes --]

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Wed, 30 Apr 2003, niklas.morberg@axis.com wrote:
>> The first thing that got me was that messages are no longer
>> marked as read just by viewing them. This is good and just
>> something that I needed to learn.
>
> I'm not sure what you mean, messages should get the read-mark when
> they are viewed.  This is exactly what should happen, so they are
> considered ham and moved out of the spam group.

What I was trying to say was: pressing space in the Summary
buffer (what I usually do to ''read'' messages) will not
mark messages as read but will display the message for you.
Pressing `d' will set the read-mark for the message.

> What you call "explicitly marking messages read" is considered a
> delete operation internally in Gnus, thus the del-mark.

Ok, that explains a lot.

BTW, I think I found an error in the documentation for
spam-use-regex-headers, suggested patch included.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Fixed docstring references --]
[-- Type: text/x-patch, Size: 656 bytes --]

cd c:/cygwin/usr/share/site-lisp/
diff -u -b "c:/cygwin/usr/share/site-lisp/spam.el~" "c:/cygwin/usr/share/site-lisp/spam.el"
--- c:/cygwin/usr/share/site-lisp/spam.el~	2003-05-06 11:04:33.000000000 +0200
+++ c:/cygwin/usr/share/site-lisp/spam.el	2003-05-06 15:15:43.000000000 +0200
@@ -144,7 +144,7 @@
 
 (defcustom spam-use-regex-headers nil
   "Whether a header regular expression match should be used by spam-split.
-Also see the variable `spam-spam-regex-headers' and `spam-ham-regex-headers'."
+Also see the variables `spam-regex-headers-spam' and `spam-regex-headers-ham'."
   :type 'boolean
   :group 'spam)
 

Diff finished at Tue May 06 15:15:56

[-- Attachment #3: Type: text/plain, Size: 8 bytes --]


Niklas

  reply	other threads:[~2003-05-06 13:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-29  7:58 Ham messages not being moved anymore Niklas Morberg
2003-04-29 18:29 ` Ted Zlatanov
2003-04-30  8:53   ` Niklas Morberg
2003-04-30 15:46     ` Ted Zlatanov
2003-05-06 13:18       ` Niklas Morberg [this message]
2003-05-08 13:35         ` [PATCH] spam.el docstring fix 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=uy91kz011.fsf_-_@axis.com \
    --to=niklas.morberg@axis.com \
    /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).