>>>>> "FFI" == Francois Felix Ingrand <[EMAIL PROTECTED]> writes:
MG> Michael Grasso writes:
MG> When using framepop v2.2 together with bbdb 1.48 and VM v5.40
MG> (according to framepop-version, bbdb-version and vm-version) a new
MG> frame is popped up for the bbdb information of each address, as well
MG> as a buffer in the mail reading frame. ie. a redundant copy of the
MG> *BBDB* buffer appears.
FFI> I reported this problem to both Jamy and the Framepop's author, but
FFI> have not received any fix yet.
Actually, there is a workaround. If you don't want the BBDB window to pop
up in the Framepop window, use the framepop suggested method of preventing
a buffer from being displayed:
(setq framepop-lines
'(lambda (buf)
(if (string= (buffer-name buf) "*BBDB*") nil
(save-excursion
(set-buffer buf)
(+ (count-lines (point-min) (point-max)) 1)))))
If you LIKE bbdb to pop up in a separate window, you need to disable
bbdb-pop-up-bbdb-buffer. I use the advice package:
(defadvice bbdb-pop-up-bbdb-buffer (around ad-bbdb-popup act comp)
"Turn off bbdb-pop-up-bbdb-buffer when using framepop."
(if (featurep 'framepop) nil
ad-do-it))
You can also do a simple re-define of the function when framepop is a
feature.... (I haven't tried this, so take it with a grain of salt.)
(if (featurep 'framepop) (defun bbdb-pop-up-bbdb-buffer (&optional x)
nil))
Jack Vinson [EMAIL PROTECTED]
The Purple Puddle Eater and Captain Jack
"Skin ain't got no tailored pockets." - Eat _Sell_Me_a_God_
