Subject: Re: The cross-posted Static Typing discussion From: Erik Naggum <email@example.com> Date: 1997/11/26 Newsgroups: comp.lang.lisp Message-ID: <firstname.lastname@example.org> * Kent M. Pitman | I wish all cross-posted conversations would go away. If anyone has the | Emacs lisp code to make cross-posted news postings get killed, I'd like | to see that. I tried (gnus-kill "Newsgroups" ",") but it complains that | "Newsgroups" is not a header field. that looks like a pretty old Gnus, but maybe this applies to old Gnus versions, too: Gnus reads headers with the NNTP command XOVER, which returns entries (lines) from a database of (tab-delimited) extracted header values called NOV (News OverView). which headers are extracted is a system configuration option, but certain headers are required and standard. I believe Xref is among those headers, provided that your NNTP server adds it to incoming articles in the first place. (it's a local header, like Path.) the Xref header looks like this (your article, at my news server): Xref: ifi.uio.no comp.lang.lisp:29614 with additional newsgroups and article numbers appended in like manner. it follows that a cross-posted articles differs from a non-cross-posted article in that it has at least three colons in this header line. (two colons if we only look only at the header's value.) so (gnus-kill "xref" ":[^:]+:[^:]+:") should kill cross-posted articles, leaving non-cross-posted articles behind. it works like that here, at least. you might want to check that articles actually have sane Xref headers and that the NOV database has Xref headers. #\Erik -- if you think this year is "97", _you_ are not "year 2000 compliant". see http://sourcery.naggum.no/emacs/ for GNU Emacs 20-related material.