Re: bbdbv3 and wanderlust

Kazuhiro Ito <[email protected]>
Newsgroups gmane.mail.wanderlust.general.japanese
Message-ID <[email protected]>
I investigated the issue.  The root cause seems that related functions
don't assume to be called from message buffer.  There are 2 actual
problems.

1. As you desribed, bbdb/wl-header assumes to be called from summary
buffer, but actually it may be called from message buffer too.  My
previous post should resolve it.

2. wl-message-redisplay-hook's functions are called from message
buffer.  When bbdb-mua-auto-update is called from message buffer,
bbdb-mua function is called from the same buffer via
bbdb-mua-update-records.  Because message buffer's major mode is
mime-view-mode, bbdb-mua signals error.  Here is minimal patch.
(Strictly, mime-view-mode is provided by SEMI and not specific to
Wanderlust.  But BBDB does not support other MUA which uses SEMI.)

diff --git a/lisp/bbdb-mua.el b/lisp/bbdb-mua.el
index 2f3378b..aab05ed 100644
--- a/lisp/bbdb-mua.el
+++ b/lisp/bbdb-mua.el
@@ -69,7 +69,7 @@
     (rmail rmail-mode rmail-summary-mode)
     (mh mhe-mode mhe-summary-mode mh-folder-mode)
     (mu4e mu4e-view-mode)  ; Tackle `mu4e-headers-mode' later
-    (wl wl-summary-mode wl-draft-mode)
+    (wl wl-summary-mode wl-draft-mode mime-view-mode)
     (message message-mode mu4e-compose-mode notmuch-message-mode)
     (mail mail-mode))
   "Alist of MUA modes supported by BBDB.


> > If you use sticky summary feature, summary buffer's name is not euqal
> > to wl-summary-buffer-name.  Replacing bbdb/wl-header function with the
> > below code should fix your problem.
> Do you mean the wl-summary-always-sticky-folder-list variable?

Yes.

--
Kazuhiro Ito
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.