Gnus development mailing list
 help / color / mirror / Atom feed
From: lee <lee@yun.yagibdah.de>
To: ding@gnus.org
Subject: "selecting deleted buffer" and buffers with sent messages staying
Date: Fri, 01 Jul 2011 20:01:57 +0200	[thread overview]
Message-ID: <877h816fsa.fsf@yun.yagibdah.de> (raw)

Hi,

is it normal for buffers with sent messages to be left over after
sending the message?  Over time, more and more abandoned buffers
accumulate.

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.



             reply	other threads:[~2011-07-01 18:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01 18:01 lee [this message]
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
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=877h816fsa.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).