On Sun Jul 8 2012 Sam Steingold wrote: > When I receive a "confirmation message" from "no-re...@foo.com", > I create a record and copy into its notes the url and all the relevant > information about the service I just registered for. > Since bbdb creates a record with first name "no-reply" and last > name "",
This should be the other way round: first name "" and last name "no-reply". Why is it reversed for you? > loading the file becomes very slow because bbdb pauses for a > second to report that I have a dozen duplicates for "webmaster", > "no-reply", "bugzilla-daemon" &c &c. I don't think it makes much > sense to add first name/last name to such records. It appears that binding bbdb-allow-duplicates to t is the easiest solution here. > It seems that treating the e-mail names just like AKAs is better. > I.e., right now a record is assumed to already have name X if X matches > either bbdb-record-name or one of bbdb-record-aka. > > Proposal: additionally, assume a record to already have name X if X > matches one of This is supposed to be relevant under which circumstances? How is this supposed to address the issue you describe above? If for whatever reason Joe Smith has the email address f...@bar.com I wouldn't like to have Joe's record match a search for name Foo. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
