From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: nocem in Gnus: should it go away?
Date: Thu, 14 Dec 2006 19:21:55 +0000 [thread overview]
Message-ID: <g69vekeffl8.fsf@lifelogs.com> (raw)
In-Reply-To: <b4mpsb0mtzi.fsf@jpl.org> (Katsumi Yamaoka's message of "Mon\, 04 Dec 2006 08\:37\:21 +0900")
On 3 Dec 2006, yamaoka@jpl.org wrote:
>>>>> In <g69fybz1o6o.fsf@lifelogs.com> Ted Zlatanov wrote:
>
>> /gnus/lisp> grep -i nocem *.el|wc
>> 165 754 9124
>
>> That's a lot of code for a feature no one uses. Should it go away?
>> Or should it be revisited, updated, and made useful?
>
> I still use NoCeM. It is mostly for the fj hierarchy, however
> there's no useful article in fj.news.lists.filters recently (the
> last one was posted at 29 Aug). So, I'll not be troubled even
> if the feature is removed.
>
> Please note that gnus-nocem.el was incomplete until I fixed it,
> as far as I knew.
>
>> Maybe it can integrate with spam.el for instance.
>
> That's great.
Well, spam.el can add an exit processor for reporting spam that would
post in the appropriate newsgroup. Do you know how this works, or is
there a document? I would also be interested in finding out how you
can undo such a posting, and if there's a register/unregister process
for ham through NoCeM. If Gnus already has such functionality, I
don't know it.
Thanks
Ted
next prev parent reply other threads:[~2006-12-14 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 18:11 Ted Zlatanov
2006-12-01 19:16 ` David Z Maze
2006-12-14 19:24 ` Ted Zlatanov
2006-12-03 23:37 ` Katsumi Yamaoka
2006-12-14 19:21 ` Ted Zlatanov [this message]
2006-12-15 5:05 ` Katsumi Yamaoka
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=g69vekeffl8.fsf@lifelogs.com \
--to=tzz@lifelogs.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).