Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Display something besides Subject line on request
Date: Fri, 02 Nov 2001 16:37:54 -0500	[thread overview]
Message-ID: <m3k7x897lj.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <m14rocg9k4.fsf@reader.newsguy.com> (Harry Putnam's message of "Fri, 02 Nov 2001 13:14:03 -0800")

Harry Putnam <reader@newsguy.com> wrote:
> Unless you mean it would be more available since it is in .overview.
> That may be a factor especially for speed.  But I'm thinking this
> would be better if it was not required to be in .overview.  That is,
> this function would plow thru the messages in the limited buffer, and
> find the Keywords lines in real time.

I would view that as a hack to compensate for backends that allow
their NOV data to become stale.  Better to keep the NOV data up to
date, since it matters for *all* uses of NOV data, not just this one.
But maybe I'm biased. :)

> Over time that would probably be faster since it would lack the
> overhead of having to find and keep another field in .overview.  It
> would only happen on demand.

Hm, maybe.  More generally, we occasionally want to operate on
information which is normally not of interest, and thus not stored
with the NOV data - so it should be possible to do that without too
much trouble.  OTOH, when the information we want to operate on is
stored with the NOV data, we shouldn't have to pay the penalty of
rescanning the original message header; that should be done only when
necessary.  Maybe it could be determined automatically by looking at
gnus-extra-headers.  NOV data still ought to be kept up to date in any
case, IMO.


paul



  reply	other threads:[~2001-11-02 21:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-02 19:07 Harry Putnam
2001-11-02 19:56 ` Paul Jarc
2001-11-02 21:14   ` Harry Putnam
2001-11-02 21:37     ` Paul Jarc [this message]
2001-11-03  1:53       ` Harry Putnam
2001-11-02 22:24 ` ShengHuo ZHU
2001-11-02 22:40 ` Kai Großjohann

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=m3k7x897lj.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).