Michael Grasso writes:
>
>I'm not sure whose "fault" this behaviour is, but it's a little
>irritating:
>
>When using framepop v2.2 together with bbdb 1.48 and VM v5.40
>(according to framepop-version, bbdb-version and vm-version) a new
>frame is popped up for the bbdb information of each address,
I'm not sure whose "fault" this behaviour is, but it's a little
irritating:
When using framepop v2.2 together with bbdb 1.48 and VM v5.40
(according to framepop-version, bbdb-version and vm-version) a new
frame is popped up for the bbdb information of each address, as well
as a buffer in the mai
With bbdb-use-pop-up set, the bbdb/mh-update-record that's called from
the insinuation around mh-display-message usually works. But, if the
(v.19.21) frame holding the mail folder is presently iconified, focus
ends up in *BBDB* instead of in the mh folder window where it started.
I can't figure o
As I discovered last week, mh-e and bbdb-use-pop-up don't play well
together. I've chased down seven mh-e routines with trouble, and a
defadvice for them (the same one in all cases). Together these seem
to make everything work. Should(n't) these be added to bbdb-mhe.el?
Since the advice is ide
