Gnus development mailing list
 help / color / mirror / Atom feed
From: lee <lee@yun.yagibdah.de>
To: ding@gnus.org
Subject: Re: "selecting deleted buffer" and buffers with sent messages staying
Date: Fri, 08 Jul 2011 18:23:14 +0200	[thread overview]
Message-ID: <87zkkolp1p.fsf@yun.yagibdah.de> (raw)
In-Reply-To: <m3sjqkqs0b.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 06 Jul 2011 00:31:16 +0200")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> lee <lee@yun.yagibdah.de> writes:
>>
>> Sometimes I'm also getting a message "selecting deleted buffer" when
>> sending a message, and the message I just sent continues to be
>> displayed.  It's as if the buffer I was composing the message in is
>> supposed to be deleted but is not.
>
> (setq debug-on-error t)
>
> and post the backtrace.

Here it is:

,----
| Debugger entered--Lisp error: (error "Selecting deleted buffer")
|   nnml-add-nov("sys.expired" 373 [nil "Re: alternative to kaffeine?" "lee <lee@yun.yagibdah.de>" "Fri, 08 Jul 2011 17:55:27 +0200" "<87ei20n4l1.fsf@totally-fudged-out-message-id>" "<87vcvdq9mt.fsf@yun.yagibdah.de> <pan.2011.07.08.14.10.41@gmail.com>" 1266 34 "yun.yagibdah.de sys.expired:373" ((To . "debian-user@lists.debian.org"))])
|   nnml-save-mail((("sys.expired" . 373)) "yun")
|   nnml-request-accept-article("sys.expired" "yun" nil)
|   gnus-request-accept-article("sys.expired" nil nil t)
|   nnmail-expiry-target-group("sys.expired" "drafts")
|   nnmh-request-expire-articles((24) "drafts" nil t)
|   apply(nnmh-request-expire-articles ((24) "drafts" nil t))
|   nnoo-parent-function(nndraft nnmh-request-expire-articles ((24) "drafts" nil t))
|   nndraft-request-expire-articles((24) "drafts" nil t)
|   message-disassociate-draft()
|   message-send(nil)
|   message-send-and-exit(nil)
|   call-interactively(message-send-and-exit nil nil)
`----

,---- [ ~/.gnus ]
| [...]
| (setq message-max-buffers 3)
| [...]
| (setq nnmail-expiry-target "sys.expired")
| [...]
`----

The debugger window showed up when I pressed C-c C-c to send the message
I had been writing.  I had to quit gnus and close the emacs frames to be
able to write a message again, though I didn't quit the emacs daemon
process.  Weird ...

BTW, since it may be related, I'm seeing drafts accumulating in the
drafts folder.  It's as if they aren't always deleted when the message
is sent.  I have a habit of automatically pressing C-x C-s somewhat
frequently I developed about 20 years ago when it was much more needed
than nowadays. Perhaps gnus doesn't like that very much? ;)

Hm, yes, the message I had been writing still has an (outdated) draft in
the drafts folder from saving it while writing it.



  parent reply	other threads:[~2011-07-08 16:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01 18:01 lee
2011-07-05 22:31 ` Lars Magne Ingebrigtsen
2011-07-07 15:12   ` lee
2011-07-19 16:37     ` Lars Magne Ingebrigtsen
2011-07-19 18:46       ` lee
2011-07-08 16:23   ` lee [this message]
2011-07-19 16:45     ` Lars Magne Ingebrigtsen
2011-07-19 22:16       ` lee
2011-07-19 22:20         ` Lars Magne Ingebrigtsen
2011-07-19 22:37           ` lee

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=87zkkolp1p.fsf@yun.yagibdah.de \
    --to=lee@yun.yagibdah.de \
    --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).