From: Michael Cook <michael@waxrat.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: nndraft:drafts broken?
Date: Fri, 10 Feb 2012 13:04:18 -0500 [thread overview]
Message-ID: <8762fe7efx.fsf@waxrat.com> (raw)
In-Reply-To: <87fwein037.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 10 Feb 2012 17:07:40 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Michael Cook <michael@waxrat.com> writes:
>
>> I'll try single stepping into gnus-topic-select-group. (But it's
>> been about a decade since the last time I tried single stepping
>> throught the gnus code... :-))
>
> Try stepping through `nndraft-retrieve-headers' instead...
In the process of trying to debug this problem, it went away. :-/
As an experiment, I used `B c' to copy a couple messages into
nndraft:drafts. The first message didn't make a difference (except
that my nndraft-retrieve-headers breakpoint was hit; until I copied
the first message, that breakpoint wasn't being hit). Then I copied
the second message and the problem went away entirely. Hmm.
Michael
prev parent reply other threads:[~2012-02-10 18:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 1:02 Michael Cook
2012-02-10 3:32 ` Lars Ingebrigtsen
2012-02-10 9:27 ` Michael Cook
2012-02-10 15:29 ` Lars Ingebrigtsen
2012-02-10 15:33 ` Michael Cook
2012-02-10 15:34 ` Lars Ingebrigtsen
2012-02-10 15:41 ` Michael Cook
2012-02-10 16:07 ` Lars Ingebrigtsen
2012-02-10 18:04 ` Michael Cook [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=8762fe7efx.fsf@waxrat.com \
--to=michael@waxrat.com \
--cc=ding@gnus.org \
--cc=larsi@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).