I've found a serious bug in BBDB version 2.2 ($Date: 2001/01/24
23:14:00 $) - it seems to be getting completion wrong. Using either a
version 5 or version 6 database with the following single entry:
foo fum
net: foo@baz, oldfoo@bar
timestamp: 05 Feb 2001
and bbdb-completion-type set to primary-or-name, if I start to compose
a message to `foo' and then hit ESC TAB (once!) to invoke
bbdb-complete-name, the name expands to
foo fum <oldfoo@bar>
in other words using the second entry in the net list, not the primary
one.
Presumably this behaviour is due to the implementation of the new
"cycling through nets" functionality? It doesn't seem to happen with
every record, eg it doesn't seem to happen in this case if the name
field is `foo' rather than `foo fum' - but it is serious, as it led to
me sending a mail to an out-of-date address by mistake.
Can I be the first one to be too late to suggest that overloading
bbdb-complete-name with the cycling through nets functionality is a
really dumb idea?
I like the fact that BBDB is getting so much work done on it right
now, but I'm somewhat dismayed at the apparent lack of coherent design
effort, and the fact that 3 out of the last 2 new features I have
tried have given me backtraces or erroneous results (I don't count
this latest example as me trying new functionality - I wasn't trying
to use the net cycling feature when it bit me).
Patrick
_______________________________________________
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/
