From: Julien Danjou <julien@danjou.info>
To: ding@gnus.org
Subject: Wrong behaviour while fetching message with IMAP
Date: Thu, 27 Jan 2011 12:14:12 +0100 [thread overview]
Message-ID: <sa3r5byy4xn.fsf@cigue.easter-eggs.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
Clicking on a message id in a mail, does very weird thing it seems.
Simplified backtrace:
* gnus-read-header("<92164B15-45D1-4D76-9AF6-8E1E098C04BD@telia.com>")
gnus-summary-insert-by-id("<92164B15-45D1-4D76-9AF6-8E1E098C04BD@telia.com>")
gnus-summary-refer-article("92164B15-45D1-4D76-9AF6-8E1E098C04BD@telia.com")
read-header returns data, whereas it should probably returns nil. Then a
mail with no info is inserted into the summary.
--
Julien Danjou
❱ http://julien.danjou.info
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2011-01-27 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 11:14 Julien Danjou [this message]
2011-01-28 1:22 ` Lars Ingebrigtsen
2011-01-28 15:46 ` Andrew Cohen
2011-01-28 17:52 ` James Cloos
2011-01-28 21:58 ` Lars Ingebrigtsen
2011-01-29 0:26 ` James Cloos
2011-01-30 0:41 ` Lars Ingebrigtsen
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=sa3r5byy4xn.fsf@cigue.easter-eggs.fr \
--to=julien@danjou.info \
--cc=ding@gnus.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).