bbdb-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Problem with bbdb and wanderlust


From: Fred Gilham
Subject: Problem with bbdb and wanderlust
Date: Tue, 09 Jun 2020 13:08:51 -0700
User-agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (Gojō) APEL/10.8 EasyPG/1.0.0 Emacs/28.0.50 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)

Some time ago I started seeing errors of the type

bbdb-bbdb-message-header: No buffer named Summary

As a result some bbdb functionality disappeared, though some continued
to work. But what most concerned me was that I was unable to forward
emails. Eventually I tracked it down as follows.

The function bbdb-message-header dispatches on the mua, and for
wanderlust it points to bbdb/wl-header.

That function uses the wl-summary-buffer-name variable to find the
name of the summary buffer, but that variable is set to "Summary".
There is no buffer named "Summary"; instead all the buffers use what
is called the "sticky buffer name" such as
"Summary:%INBOX:randomuser/clear@imap.gmail.com:993!"





Changing 

      wl-summary-buffer-name 

to

      (wl-summary-sticky-buffer-name
       (elmo-folder-name-internal wl-summary-buffer-elmo-folder))

makes everything work as expected.

Here's a diff:

--- bbdb-wl.el-old      2020-02-18 09:50:43.252186491 -0800
+++ bbdb-wl.el  2020-06-09 06:16:49.859572928 -0700
@@ -36,8 +36,11 @@
   (autoload 'elmo-message-entity-field "elmo-msgdb"))
 
 ;;;###autoload
+
 (defun bbdb/wl-header (header)
-  (with-current-buffer wl-summary-buffer-name
+  (with-current-buffer
+      (wl-summary-sticky-buffer-name
+       (elmo-folder-name-internal wl-summary-buffer-elmo-folder))
     (elmo-message-entity-field
      (elmo-message-entity wl-summary-buffer-elmo-folder
                           (wl-summary-message-number))



-- 
   just make me lighter
   make me lighter still
     'til the yellow of the sun takes me

   [oh what Lazarus saw! I cannnot bear this anymore!]
                                                      -- Linshuang Lu



reply via email to

[Prev in Thread] Current Thread [Next in Thread]