From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Odd bug with lazy-loaded messages
Date: Mon, 03 Aug 2009 10:18:50 -0700 [thread overview]
Message-ID: <1249319474-sup-8322@masanjin.net> (raw)
In-Reply-To: <1248716007-sup-5156@javelin>
Sorry I didn't respond to this earlier.
Reformatted excerpts from Edward Z. Yang's message of 2009-07-27:
> Specifically, the "default" opened message when I open a thread
> gets a weird misrendering of the headers that looks like:
>
> To: foo
> foo <foo at example.com>
> foo
>
> And so forth, for all lines in To and Cc.
This is because we store a couple variants of the address in the index
(e.g. the email address to the left of the @), so that a search on any
of them will bring up the message. Without #load_from_source!, the
message is loaded from the index, so it reflects those fields. So it's
basically a hack at this point. You could further hack it by undoing
that transformation. Or we could add the original version of the fields
to the index in a separate, non-searchable field, incurring the
associated storage penalties.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-08-03 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 17:36 Edward Z. Yang
2009-08-03 17:18 ` William Morgan [this message]
2009-08-08 6:07 ` Edward Z. Yang
2009-08-09 8:40 ` Edward Z. Yang
2009-12-15 22:40 ` Edward Z. Yang
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=1249319474-sup-8322@masanjin.net \
--to=wmorgan-sup@masanjin.net \
/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