From: Svend Tollak Munkejord <stm+direct_reply@bacchus.pvv.org>
Subject: Re: Can I get rid of the \201 ?
Date: Mon, 15 Mar 2004 15:20:39 +0100 [thread overview]
Message-ID: <hddvfl6fayw.fsf@bacchus.pvv.ntnu.no> (raw)
In-Reply-To: <hddoerzs6s2.fsf@bacchus.pvv.ntnu.no>
I wrote:
> The body of the message is supposed to be "Hei øæå". The Subject is
> interesting, because it appears all right in the Article buffer, whereas
> in the Summary buffer it appears as "Test øæå".
>
> Can I get rid of this?
I have found that the reason for the misbehaviour is my fancy split-on-body
function. However, I don't understand why. Can anyone help?
Here it is:
(defun stm-split-on-body (relevant-terms-regexp groupname &optional regex)
"Splits e-mail *not* fitting RELEVANT-TERMS-REGEXP to group
GROUPNAME (string).
If REGEX is nil, relevant-terms-regexp must be a list instead. Well.
Used in: nnmail-split-fancy"
(save-excursion
; (" *nnmail incoming*") for e-mail:
(let ((buf (or (get-buffer nnmail-article-buffer)
; (" *Original Article*") for trace (B t)
(get-buffer gnus-original-article-buffer)
; for respool -- Aargh. Does not work for nnmaildir:
(get-buffer " *nnmaildir move*"))))
(if (not buf)
(progn (message "Oops, cannot find message buffer") nil)
(set-buffer buf)
(save-restriction
(if (string= (buffer-name buf) gnus-original-article-buffer)
(widen))
; in case we have base64 etc.
(run-hooks 'gnus-article-decode-hook)
(goto-char (point-min))
(if regex
(when (not (re-search-forward relevant-terms-regexp nil t));
groupname)
(when (not (all-words-present-p relevant-terms-regexp));
groupname)))))))
Regards,
--
Svend Tollak Munkejord
next prev parent reply other threads:[~2004-03-15 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <hddoerzs6s2.fsf@bacchus.pvv.ntnu.no>
2004-02-16 12:38 ` Reiner Steib
2004-02-16 14:11 ` Svend Tollak Munkejord
2004-03-15 14:20 ` Svend Tollak Munkejord [this message]
[not found] ` <m3ptbef8sj.fsf@defun.localdomain>
2004-03-15 15:17 ` Svend Tollak Munkejord
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=hddvfl6fayw.fsf@bacchus.pvv.ntnu.no \
--to=stm+direct_reply@bacchus.pvv.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).