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 10:33:21 -0500 [thread overview]
Message-ID: <8739aig0u6.fsf@waxrat.com> (raw)
In-Reply-To: <87ty2yn1ug.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 10 Feb 2012 16:29:43 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Oh, you couldn't select the drafts group at all?
Right.
> Hm. I seem to be unable to reproduce this -- if there's anything
> in the drafts directory, it shows up in the drafts group.
>
> If you enter the group with `RET', is there anything in the " *nntpd"*
> buffer afterwards?
It's empty. It's in the modified state, if that's interesting. But empty.
Michael
next prev parent reply other threads:[~2012-02-10 15:33 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 [this message]
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
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=8739aig0u6.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).