Is there a way to make BBDB simply record an AKA when it finds a name mismatch, without doing a (sit-for 1) or the user having to go through the questions about making the name an alternate? Looking at the code, it appears that if `bbdb-quiet-about-name-mismatches' is non-nil when a mismatch is encountered, it does the sit-for in order to make the "name mismatch..." message visible to the user. If `bbdb-quiet-about-name-mismatches' is nil, you have to go through the questioning about whether you want the new name to refer to the same net address. I'd like to be able to tell BBDB to quietly add an AKA if it encounters a name mismatch for a particular address, without blocking with a sit-for. Why? Because if you customize, say, VM to show only certain headers in a message, when that sit-for is encountered, at that point all of the message headers are shown, and only *afterwards* are the headers trimmed down. The screen jumps around annoyingly, especially if you're doing this over a modem. Maybe this is actually a problem with VM or the interaction between BBDB and VM, but it seems reasonable to want to tell BBDB "just register an AKA and don't bug me about it". Perhaps `bbdb-quiet-about-name-mismatches' could take on more than just a binary value, to allow for this. -- Mike _____________________________________________________________________________ Mike Hucka | Internet: [EMAIL PROTECTED] University of Michigan AI Lab | 1101 Beal Ave., Ann Arbor, MI 48109-2110
