From: Felix Natter <fnatter@gmx.net>
To: Katsumi Yamaoka <yamaoka@jpl.org>, info-gnus-english@gnu.org
Subject: Re: Sent message still in drafts (lisp error: "Selecting deleted buffer")
Date: Tue, 26 Mar 2013 20:58:39 +0100 [thread overview]
Message-ID: <87fvzidjbk.fsf@bitburger.home.felix> (raw)
In-Reply-To: <b4m620fx72d.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Felix Natter wrote:
>> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>
>> hi Katsumi,
>
>> sorry that it took me so long!
>
>>> Felix Natter wrote:
>>>> Debugger entered--Lisp error: (error "Selecting deleted buffer")
>>>> nnml-add-nov("expired" 12197 [nil "Rheinblick-Cache" "Felix Natter <fnat...
>>>> nnml-save-mail((("expired" . 12197)) "")
>>>> nnml-request-accept-article("expired" "" nil)
>>>
>>> I'm unable to reproduce such an error. Could you get a backtrace
>>> again by loading nnml.el (or nnml.el.gz, not .elc) in advance?
>>> I.e.: M-x load-library RET nnml.el RET, and do mail.
>
>> Here it is, with (setq debug-on-error t) and M-x load-library
>> nnml.el:
hello Katsumi,
> Thanks. Though I haven't found the cause of the error in question
> yet, I found some other problems on expiring sent drafts to a group.
>
> The principal one is that a draft is not like a normal article:
>
> ・There is a separator between the header and the body.
> - You can't read its body in an expiry group.
> - Xref herder, etc. are put at the end of the body.
> ・Non-ASCII text has not been encoded properly.
> ・Attachments do not necessarily exist when re-using it.
So the problem is that when I send a draft, its content is subject
to expiry, and this does not work because a draft is not like
a normal article (and with the "G c" below we tell Gnus to delete
and not expire sent drafts)?
> It will cost to improve it.
What do you mean by "costs to improve it"?
> Er, archiving sent drafts in an expiry
> group is not the purpose of
>
> (setq nnmail-expiry-target "nnml:expired")
Yes, I am doing that:
(setq nnmail-expiry-target "nnml:expired")
> you set, isn't it? If so, how about setting a group parameter so
> that only sent drafts are deleted? To do that:
>
> ・In the Group buffer, type `G c' on the "nndraft:drafts" group
> to open the customization buffer.
> ・Find the "Expiry Target" entry, check the box, and make sure
> the value is `delete'.
> ・Press the [done] button at the beginning of the buffer.
> ・Type `s' to save the customization in the ~/.newsrc.eld file.
Thank you, that looks good, I'll try that!
If that works, then I think it's a good idea to mention this problem
in the Gnus documentation?
Many thanks again and Best Regards,
--
Felix Natter
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2013-03-26 19:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.19525.1360518618.855.info-gnus-english@gnu.org>
2013-02-13 0:18 ` Katsumi Yamaoka
2013-03-25 20:41 ` Felix Natter
[not found] ` <mailman.22829.1364244138.855.info-gnus-english@gnu.org>
2013-03-26 1:50 ` Katsumi Yamaoka
2013-03-26 19:58 ` Felix Natter [this message]
[not found] ` <mailman.22889.1364327929.855.info-gnus-english@gnu.org>
2013-03-27 0:17 ` Katsumi Yamaoka
2013-03-27 18:29 ` Felix Natter
[not found] ` <mailman.22943.1364408991.855.info-gnus-english@gnu.org>
2013-03-28 1:36 ` Expiring sent drafts does now always `delete' Katsumi Yamaoka
2013-03-31 18:19 ` Sent message still in drafts (lisp error: "Selecting deleted buffer") Felix Natter
2013-03-31 23:48 ` Katsumi Yamaoka
2013-03-31 23:59 ` Katsumi Yamaoka
2013-04-01 7:31 ` Felix Natter
[not found] ` <mailman.23203.1364801493.855.info-gnus-english@gnu.org>
2013-04-01 9:44 ` Katsumi Yamaoka
2013-04-01 12:20 ` Felix Natter
[not found] ` <mailman.23213.1364818828.855.info-gnus-english@gnu.org>
2013-04-02 1:40 ` Katsumi Yamaoka
2013-02-10 17:49 Felix Natter
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=87fvzidjbk.fsf@bitburger.home.felix \
--to=fnatter@gmx.net \
--cc=info-gnus-english@gnu.org \
--cc=yamaoka@jpl.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).