From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/7138 Path: main.gmane.org!not-for-mail From: John Griffith Newsgroups: gmane.emacs.gnus.general Subject: BBDB error: "Selecting deleted or non-existent buffer" Date: 06 Jul 1996 11:19:19 +0200 Sender: griffith@sfs.nphil.uni-tuebingen.de Message-ID: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII X-Trace: main.gmane.org 1035147492 6072 80.91.224.250 (20 Oct 2002 20:58:12 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 20:58:12 +0000 (UTC) Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by deanna.miranova.com (8.7.5/8.6.9) with SMTP id CAA30078 for ; Sat, 6 Jul 1996 02:34:34 -0700 Original-Received: from filippo.sfs.nphil.uni-tuebingen.de (filippo.sfs.nphil.uni-tuebingen.de [134.2.129.45]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Sat, 6 Jul 1996 11:19:25 +0200 Original-Received: (from griffith@localhost) by filippo.sfs.nphil.uni-tuebingen.de (8.7.5/8.7.3) id LAA11175; Sat, 6 Jul 1996 11:19:20 +0200 (MET DST) Original-To: ding@ifi.uio.no In-Reply-To: Kai Grossjohann's message of 02 Jul 1996 10:31:02 +0200 Original-Lines: 22 Xref: main.gmane.org gmane.emacs.gnus.general:7138 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:7138 I've been getting this error for a while. I don't get a bbdb window when the sender of an article is in my db. Plus if I do ":" I get the following backtrace: Signalling: (error "Selecting deleted or non-existent buffer") bbdb/gnus-update-record(t) bbdb/gnus-pop-up-bbdb-buffer(t) bbdb/gnus-update-record(t) #() call-interactively(bbdb/gnus-show-sender) I'm using Gnus 5.2.31, bbdb 1.51 and the latest gnus-bbdb.el. Here's what I have related to bbdb in my .gnus: (require 'gnus-bbdb) (gnus-bbdb-insinuate-summary-buffer) (add-hook 'gnus-startup-hook 'bbdb-insinuate-gnus) (setq bbdb/gnus-header-prefer-real-names t) Has anyone else seen this error? Any ideas? -- John