guile-email discussion
 help / color / mirror / Atom feed
From: Arun Isaac <>
To: Ricardo Wurmus <>,
Subject: Re: Mumi inserts spurious underscore in bug title
Date: Thu, 29 Dec 2022 19:36:07 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Ricardo,

Thanks for the bug report!

It's very strange, but I'm not able to reproduce this. I tried the
following. bug_49114.mbox is downloaded from;bug=49114

--8<---------------cut here---------------start------------->8---
(use-modules (email email))

 (parse-email-headers "Subject: bug#49114: =?UTF-8?Q?=E2=80=98guix_?= =?UTF-8?Q?lint=E2=80=99?= should catch certificate validation exceptions

(for-each (lambda (bv)
            (pk (assoc-ref (email-headers (parse-email bv))
          (call-with-input-file "bug_49114.mbox"
--8<---------------cut here---------------end--------------->8---

Even at , only the "bug title" has the
spurious underscore. The subject of the first message does not. Is the
bug title something stored in the xapian index? Could it be that this
was an older bug that has corrupted the xapian index?

If I understand correctly, mumi does not rebuild its xapian index. I
think it should do so from time to time. It would help prevent old bugs
from getting persisted in storage.

Cheers, and wish you a Happy New Year! :-)

  reply	other threads:[~2022-12-29 19:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-24 22:53 Ricardo Wurmus
2022-12-29 19:36 ` Arun Isaac [this message]
2023-01-01 12:15   ` Ricardo Wurmus
2023-01-02 17:43     ` [PATCH 0/1] Do not check for MIME encoded words Arun Isaac
2023-01-02 17:43     ` [PATCH 1/1] debbugs: Do not check for MIME encoded words in subject Arun Isaac
2023-01-02 19:34       ` Ricardo Wurmus

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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