Fritz Knabe writes:
> Damon Lipparelli writes:
>> Now, when I try to look at a message (with ".") I get the
>> following error message displayed in the minibuffer: "Wrong type
>> argument: listp, 27248" It doesn't seem to matter who the message
>> is from, but my BBDB file is pretty small, so I don't think there
>> are BBDB entries for any of the people that I am getting mail
>> from.
> Here is a patch. The problem arose from the different results that
> Lucid Emacs and FSF Emacs return for the file-attributes function.
The first patch I posted was incorrect. Here's a patch to the patch
(i.e., apply this one after applying the previous one). If you don't
use MH, you can ignore this.
Fritz
*** bbdb/bbdb-mhe.el.orig Wed Dec 8 07:24:17 1993
--- bbdb/bbdb-mhe.el Wed Dec 8 07:38:49 1993
***************
*** 24,40 ****
(require 'mh-e) ; Note- we advise several functions in this file.
(require 'advice)
! (if (string-match "Lucid" emacs-version)
! (defmacro bbdb/mh-cache-key (message)
! "Return a (numeric) key for MESSAGE"
! (`(let* ((attrs (file-attributes (, message)))
! (status-time (nth 6 attrs)))
! (logxor (nth 10 attrs) (car status-time) (cdr status-time)))))
! (defmacro bbdb/mh-cache-key (message)
! "Return a (numeric) key for MESSAGE"
! (`(let* ((attrs (file-attributes (, message)))
! (status-time (nth 6 attrs)))
! (logxor (nth 10 attrs) (car status-time) (car (cdr status-time)))))))
;;;% Currently assumes msg buffer is the current buffer,
;;;% as usually (always?) is when called from the hook.
--- 24,42 ----
(require 'mh-e) ; Note- we advise several functions in this file.
(require 'advice)
! (defmacro bbdb/mh-cache-key (message)
! "Return a (numeric) key for MESSAGE"
! (`(let* ((attrs (file-attributes (, message)))
! (status-time (nth 6 attrs))
! (status-time-2 (cdr status-time)))
! (logxor (nth 10 attrs)
! (car status-time)
! ;; We need the following test because Lucid returns the
! ;; status time as a dotted pair, whereas FSF and Epoch
! ;; return it as list.
! (if (integerp status-time-2)
! status-time-2
! (car status-time-2))))))
;;;% Currently assumes msg buffer is the current buffer,
;;;% as usually (always?) is when called from the hook.
