Hmm, that was bizarre. Here's what I'd intended to appear on the list:
On December 22, [EMAIL PROTECTED] said:
>
> Yep, I'd managed to dig this up myself, and discovered that the
> breakage is not related to the file format change. I need to find out
> what it IS related to before I can fix it.
Did I miss the mime encoding on this?
> T24gRGVjZW1iZXIgMjIsIHBhdHJpY2tAY2hhb3Mub3JnLnVrIHNhaWQ6DQo+IA0KPiAgIG1hcGNh
--snipped--
Chris
___
bbdb-info mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/bbdb-info
On December 22, [EMAIL PROTECTED] said:
>
> mapcar(#[(rec) "\304 \205
> !#\207" [rec match-fun r override bbdb-merge-record] 4] ())
> bbdb-merge-file("/tmp/.bbdb")
> call-interactively(bbdb-merge-file)
> execute-extended-command(nil)
> call-interactively(execu
Waider:
> > The main reason why I upgraded to 2.2 was the new bbdb-merge
> > functionality, but when I try bbdb-merge-file I get the error
> >
> > Wrong type argument: listp, -129453780
>
> Can you please set stack-track-on-error to t and reproduce this so I
> can figure out exactly where it
On December 10, [EMAIL PROTECTED] said:
>
> The main reason why I upgraded to 2.2 was the new bbdb-merge
> functionality, but when I try bbdb-merge-file I get the error
>
> Wrong type argument: listp, -129453780
Can you please set stack-track-on-error to t and reproduce this so I
can figure o
The main reason why I upgraded to 2.2 was the new bbdb-merge
functionality, but when I try bbdb-merge-file I get the error
Wrong type argument: listp, -129453780
Has anyone else had this problem? I haven't tried to investigate it
yet, but if I replace my real .bbdb files with test files wit
Patrick Campbell-Preston writes:
> The main reason why I upgraded to 2.2 was the new bbdb-merge
> functionality, but when I try bbdb-merge-file I get the error
> Wrong type argument: listp, -129453780
M-: (setq debug-on-error t)
This will get you a stack trace, which can help narrow down