Gnus development mailing list
 help / color / mirror / Atom feed
From: John Griffith <griffith@sfs.nphil.uni-tuebingen.de>
Cc: info-bbdb@xemacs.org
Subject: Re: BBDB error: "Selecting deleted or non-existent buffer"
Date: 08 Jul 1996 17:29:52 +0200	[thread overview]
Message-ID: <tjbuhqlq4v.fsf@sfs.nphil.uni-tuebingen.de> (raw)
In-Reply-To: John Griffith's message of 06 Jul 1996 11:19:19 +0200


On the ding list, I asked if anyone else got the error:
   "Selecting deleted or non-existent buffer"
in the Gnus summary buffer when doing ":".

Sudeep Kumar Palat <palat@idt.unit.no> solved this problem for me.
(Thanks Sudeep!).

The problem is with multiple article buffers in Gnus.  In bbdb-gnus.el, the
line:

   (set-buffer "*Article*")

needs to be changed to:

   (set-buffer gnus-article-buffer)

to handle these.


      reply	other threads:[~1996-07-08 15:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-06  9:19 John Griffith
1996-07-08 15:29 ` John Griffith [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=tjbuhqlq4v.fsf@sfs.nphil.uni-tuebingen.de \
    --to=griffith@sfs.nphil.uni-tuebingen.de \
    --cc=info-bbdb@xemacs.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).