Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: gnus-summary-respool-trace for nnimap?
Date: Wed, 21 Nov 2001 13:43:40 -0500	[thread overview]
Message-ID: <m3k7wkq80d.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <vafpu6c87jp.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Wed, 21 Nov 2001 16:31:22 +0100")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
> Niklas Morberg <niklas.morberg@axis.com> writes:
>> Is there any way to let the regexes match against what I see in the
>> message buffer instead of the raw contents?
>
> Decoding could take a lot of time, so the current strategy is to do
> the matching on the raw message.
>
> One must avoid to decode the body -- or do you want Emacs to play a
> sound while splitting, just because the incoming message happens to
> contain a sound?  As a less extreme example, rendering text/html is
> computationally expensive.

Decoding is not displaying.  Or at least, it shouldn't be, I think.
Of course, we do still want to avoid decoding the body, just because
we're not interested in the body at this point, so it would be wasted
effort.


paul



      parent reply	other threads:[~2001-11-21 18:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21 10:49 Niklas Morberg
2001-11-21 12:40 ` Kai Großjohann
2001-11-21 13:33   ` Niklas Morberg
2001-11-21 15:31     ` Kai Großjohann
2001-11-21 15:58       ` Matching split rules against decoded headers? (Was: Re: gnus-summary-respool-trace for nnimap?) Niklas Morberg
2001-11-21 16:33         ` Kai Großjohann
2001-11-21 18:43       ` Paul Jarc [this message]

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=m3k7wkq80d.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).