Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Felix Natter <fnatter@gmx.net>
To: info-gnus-english@gnu.org
Subject: Sent message still in drafts (lisp error: "Selecting deleted buffer")
Date: Sun, 10 Feb 2013 18:49:49 +0100	[thread overview]
Message-ID: <874nhkhxdu.fsf@bitburger.home.felix> (raw)

hi,

I am using: GNU Emacs 23.4.1 (i486-pc-linux-gnu, GTK+ Version 2.24.10)
 of 2012-09-09 on murphy, modified by Debian with Gnus v5.13.

I am often (but not always) running into the problem that although a
message has been sent (and ends up in the "sent-mail" folder), it is
still in 'drafts'. When that happens, the last message in *Messages* is:

nnml-save-mail: Selecting deleted buffer

And if I do '(setq debug-on-error t)' beforehand (but not before
starting Gnus) then I get:

Debugger entered--Lisp error: (error "Selecting deleted buffer")
  nnml-add-nov("expired" 12197 [nil "Rheinblick-Cache" "Felix Natter <fnatter@gmx.net>" "Sun, 10 Feb 2013 18:19:25 +0100" "<87pq08hyse.fsf@totally-fudged-out-message-id>" nil 0 0 "bitburger.home.felix expired:12197" ((To . "ulrike.natter@gmx.de"))])
  nnml-save-mail((("expired" . 12197)) "")
  nnml-request-accept-article("expired" "" nil)
  gnus-request-accept-article("nnml:expired" nil nil t)
  nnmail-expiry-target-group("nnml:expired" "drafts")
  nnmh-request-expire-articles((104) "drafts" nil t)
  apply(nnmh-request-expire-articles ((104) "drafts" nil t))
  nnoo-parent-function(nndraft nnmh-request-expire-articles ((104) "drafts" nil t))
  nndraft-request-expire-articles((104) "drafts" nil t)
  message-disassociate-draft()
  message-send(nil)
  message-send-and-exit(nil)
  call-interactively(message-send-and-exit nil nil)

My mails are in ~/Mail, but my drafts are in ~/News/drafts/drafts, if
that makes a difference.
I also use this:
(setq nnmail-expiry-target "nnml:expired")

Is this fixed in the Gnus contained in Emacs24?

Thanks and Best Regards!
-- 
Felix Natter

             reply	other threads:[~2013-02-10 17:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10 17:49 Felix Natter [this message]
     [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
     [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
2013-03-31 18:19           ` 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

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=874nhkhxdu.fsf@bitburger.home.felix \
    --to=fnatter@gmx.net \
    --cc=info-gnus-english@gnu.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).