Today, Ronan Waide <[EMAIL PROTECTED]> wrote:
>> Signaling: (wrong-type-argument arrayp -A)
>> bbdb-record-getprop(-A mail-alias)
>> bbdb-define-all-aliases()
>
> urgh. somehow, i get the feeling that your in-memory bbdb is getting
> corrupted somewhere along the way, because what's happened
On May 7, [EMAIL PROTECTED] said:
> Hi,
>
> using Oort gnus v0.04 and XEmacs 21.4.1 with BBDB version 2.33 ($Date:
> 2001/04/19 11:12:00 $), I get an error, every time I try to write an
> article. The error appears in my message-setup-hook (I have bbdb set up
> aliases). I get another backtrace w
On 2001-05-07, Andreas Fuchs <[EMAIL PROTECTED]> wrote:
> using Oort gnus v0.04 and XEmacs 21.4.1 with BBDB version 2.33 ($Date:
> 2001/04/19 11:12:00 $), I get an error, every time I try to write an
> article. The error appears in my message-setup-hook (I have bbdb set
> up aliases). I get anothe
On 2001-05-07, Andreas Fuchs <[EMAIL PROTECTED]> wrote:
> -- first Backtrace (opening a message):
> Signaling: (wrong-type-argument number-char-or-marker-p nil)
> bbdb-insert-record-internal([nil nil nil nil nil nil nil
Okay, thanks to edebug, I could track this bug down to:
(if (and (/= p
Hi,
using Oort gnus v0.04 and XEmacs 21.4.1 with BBDB version 2.33 ($Date:
2001/04/19 11:12:00 $), I get an error, every time I try to write an
article. The error appears in my message-setup-hook (I have bbdb set up
aliases). I get another backtrace when I open a message in the summary
buffer. Th
