From: Karl Kleinpaste <karl@jprc.com>
Subject: new NOV stuff in p0.40
Date: 25 Oct 1998 19:18:05 -500 [thread overview]
Message-ID: <vxk3e8c6urm.fsf@pocari-sweat.jprc.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3354 bytes --]
I've been trying out the new 0.40, and I'm confused. I looked through
the code to see what's being done about .overview, but I'm failing to
get a grip on what's happening.
First, why are there 2 new variables for NOV control,
gnus-extra-headers and nnmail-extra-headers? When might one
conceivably want them to be different? Do I at least understand
correctly that nnmail-e-h is used when *storing* mail messages while
gnus-e-h is used when *receiving* XOVER response?
I'm using:
(setq gnus-extra-headers '(Keywords To Newsgroups)
nnmail-extra-headers '(Keywords To Newsgroups)
gnus-ignored-from-addresses "karl@charcoal\\.com\\|karl@jprc\\.com")
Second, I have set gnus-ignored-from-addresses to several variations
on my addresses, as you see above, but yet *Summary* buffers are still
showing myself rather than where the messages were going. I'm testing
by sending mail to myself under aliases, so the message ends up both
Gcc'd and delivered into one nnml group. Sample .overview lines from
such a pair:
327 NOV tst Karl Kleinpaste <karl@charcoal.com> 25 Oct 1998 18:37:14 -500 <vxkaf2kfc2d.fsf@mesquite.charcoal.com> 5 1 Xref: mesquite.charcoal.com personal.karl:327 To: usenet@charcoal.com Keywords: basic,testing
328 NOV tst Karl Kleinpaste <karl@charcoal.com> 25 Oct 1998 18:37:14 -500 <vxkaf2kfc2d.fsf@mesquite.charcoal.com> 6 2 Xref: mesquite.charcoal.com personal.karl:328 To: usenet@charcoal.com Keywords: basic,testing
And *Summary* shows:
: : NOV tst
R + [ 1: Karl Kleinpaste ]
+ [ 2: Karl Kleinpaste ]
How do I get *Summary* to stop showing "me" and start showing
"usenet@..."? I thought the setq above would give it to me, but
apparently not so. I'm sorely tempted to re-deploy last week's little
patch for nnheader.el which led to Lars' inspiration for NOV re-work,
but I'd rather get it "right" using the new tools.
Third, of far more importance to me is the fact that I've lost
something else: I did a bit of hackery a couple years ago to give
myself general scorability on Keywords headers. My INN installations
include server-side auto-generation of Keywords by grinding article
bodies in search of computationally interesting words, creating
Keywords content on the fly for overviews, whether there's such a
header in the article or not. My overviews are ~20% larger than
without this capability, with examples now looking like this:
11676 slrn, can't disable color mode mjc@c1000907-b.sttls1.wa.home.com (Mark Crosland) Sun, 25 Oct 1998 22:43:03 GMT <slrn7377gn.7vk.mjc@c1000907-b.sttls1.wa.home.com> 760 5 Xref: news.jprc.com news.software.readers:11676 Keywords: ,ÿ,slrn,thought,colors,coming,newsrc,color,mode,seem,stop,use
This lets me do some extremely useful content-scoring without
requiring full-body searches, using a few additional entries in the
scoring keymaps and -- up to now -- a couple new macros like
mail-header-keywords (which no longer work, of course, in this brave
new world of generalized NOV handling). Example use: In
news.software.readers, I score up "gnus" in keywords highly, which
catches a surprisingly large number of references to Our Favorite
Newsreader. Is there any way to (re)gain this kind of score
capability in a generalized manner, without hacking up per-header
functions?
dazed and confused,
--karl
next reply other threads:[~1998-10-26 0:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-26 0:18 Karl Kleinpaste [this message]
1998-10-26 0:37 ` Lars Magne Ingebrigtsen
1998-10-26 1:40 ` Karl Kleinpaste
1998-10-26 2:15 ` Karl Kleinpaste
1998-10-26 2:52 ` Lars Magne Ingebrigtsen
1998-10-26 8:17 ` Kai Grossjohann
1998-10-26 8:48 ` Lars Magne Ingebrigtsen
1998-10-26 10:12 ` Kai Grossjohann
1998-10-26 2:48 ` Lars Magne Ingebrigtsen
1998-10-28 5:51 ` Karl Kleinpaste
1998-10-28 13:38 ` Karl Kleinpaste
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=vxk3e8c6urm.fsf@pocari-sweat.jprc.com \
--to=karl@jprc.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).