On Thursday, February 8 2001 01:56:39, Conrad Sauerwald wrote:
> I've included a patch to explain.  Not completely bleeding edge cvs,
> as you can see.  I'm sure someone can fix this in a more elegant way.
> bbdb notices a new address, I ask to add it, (not (bbdb-y-or-n-p evals
> to nil and bbdb goes away without actually performing the add (when,
> in let, needs to convince an if to go add it).  Or so I thought.
Thanks for the patch, indeed it was a bug.  I made a little
modification to your patch, since it was asking me for newly
created records if I want to make the new net the primary
one or not, which IMHO should not happen.

It is now in CVS.

Robert

Index: lisp/bbdb.el
===================================================================
RCS file: /cvsroot/bbdb/bbdb/lisp/bbdb.el,v
retrieving revision 1.132
retrieving revision 1.133
diff -w -r1.132 -r1.133
2791c2791
<                            (when (and (not (bbdb-y-or-n-p (concat the-first-bit
---
>                            (if (bbdb-y-or-n-p (concat the-first-bit
2793,2796c2793,2795
<                                                                   "\"? ")))
<                                       (bbdb-y-or-n-p
<                                        (format "Create a new record for %s? "
<                                                (bbdb-record-name record))))
---
>                                                       "\"? "))
>                                ;; then add the new net
>                                t
2797a2797,2799
>                              (if (bbdb-y-or-n-p
>                                   (format "Create a new record for %s? "
>                                           (bbdb-record-name record)))
2800c2802
<                                                          nil nil nil))
---
>                                                              nil nil nil)))


_______________________________________________
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/

Reply via email to