From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: bugs@gnus.org, ding@gnus.org
Subject: Re: gnus-draft-edit-message vs. gnus-summary-mail-other-window
Date: Tue, 14 Feb 2006 10:55:36 +0900 [thread overview]
Message-ID: <b4mk6bywvon.fsf@jpl.org> (raw)
In-Reply-To: <b4m64nnxtyg.fsf@jpl.org>
>>>>> In <b4m64nnxtyg.fsf@jpl.org> Katsumi Yamaoka wrote:
>>>>>> In <87oe20f3bo.fsf@jidanni.org> Dan Jacobson wrote:
>> If one is editing a message with e.g., gnus-summary-mail-other-window,
>> and then one goes to the drafts buffer and uses
>> gnus-draft-edit-message, and then sends that message from there, the
>> original buffer made with gnus-draft-edit-message is still left in the
>> buffer list, in modified state too.
>> gnus-version's value is "No Gnus v0.4"
> I found a couple of bugs and the ones that seem to be bugs in
> gnus-draft.el and possibly nndraft.el. I'm going to fix them
> and also solve your problem. Perhaps within the course of a few
> days.
I've fixed it in both the trunk and the v5-10 branch. Now you
can *not* edit and send articles in the nndraft:drafts group if
they are under edit (I didn't make it kill those mail buffers,
since Gnus doesn't do so with usual mail buffers which are being
edited).
prev parent reply other threads:[~2006-02-14 1:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87oe20f3bo.fsf@jidanni.org>
2006-02-10 12:46 ` Katsumi Yamaoka
2006-02-14 1:55 ` Katsumi Yamaoka [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=b4mk6bywvon.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=bugs@gnus.org \
--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).