Re: [BBDB] ChangeLog 2012-08-01 (was: How to merge to records with identical names?)

2012-08-01 Thread Roland Winkler
On Wed Aug 1 2012 Roland Winkler wrote:
> On Wed Aug 1 2012 Alan Schmitt wrote:
> > I have a person that was entered twice in bbdb, with the same name but
> > two different mails. I tried to put the cursor on one of the records and
> > do a "M-x bbdb-merge-record", but when I enter the second mail address,
> > I get an error:
> > 
> > Mail address "(the current mail address)" is used by "(the name of the
> > person)"
> 
> This should be fixed now.

More small changes.

2012-08-01  Roland Winkler  
* lisp/bbdb-com.el (bbdb-merge-records): Improve interactive call
and docstring.


BBDB is available at
http://savannah.nongnu.org/projects/bbdb/
To check it out, use
git clone git://git.savannah.nongnu.org/bbdb.git

--
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/


[BBDB] ChangeLog 2012-08-01 (was: How to merge to records with identical names?)

2012-08-01 Thread Roland Winkler
On Wed Aug 1 2012 Alan Schmitt wrote:
> I have a person that was entered twice in bbdb, with the same name but
> two different mails. I tried to put the cursor on one of the records and
> do a "M-x bbdb-merge-record", but when I enter the second mail address,
> I get an error:
> 
> Mail address "(the current mail address)" is used by "(the name of the
> person)"

This should be fixed now.

When I last touched the code of bbdb-merge-records, the code for
checking duplicates was broken. In the meanwhile this got fixed, but
this check doesn't make sense while merging records.

2012-08-01  Roland Winkler  
* lisp/bbdb.el (bbdb-allow-duplicates, bbdb-hash-update)
(bbdb-record-set-field): Fix docstring.
* lisp/bbdb-com.el (bbdb-merge-records): Do not through an error
when merging the old and new record results in duplicate AKAs and
email addresses.


BBDB is available at
http://savannah.nongnu.org/projects/bbdb/
To check it out, use
git clone git://git.savannah.nongnu.org/bbdb.git

--
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/


Re: [BBDB] Changelog 2012-07-31

2012-08-01 Thread Roland Winkler
On Wed Aug 1 2012 Stephen Leake wrote:
> Now that's fixed, but I suspect I'll still use separate records in
> a case like this. For example, sm...@foo.com should have a
> different work phone than j...@bar.com. But maybe I need to
> experiment more.

I do not quite see why an email address needs to be associated with
a phone number. For some records I do have a bunch of phone numbers
as well as a bunch of email addresses.

But I cannot think of situations where I wanted to have something
like an association list associating phone numbers with email
addresses.

> It would be nice to not have (home) show up in the final
> email address; putting a real name in the Mail field could fix that
> (assuming it overrides the real name in the record).

As my example showed, you can combine canonical mail addresses
sm...@foo.com with real names like "John Smith ". 
I do not know in which context you think of "overriding" the real
name. If you send an email to sm...@foo.com, the message header will
become

To: John Smith 

no matter, what the name field of the record contains.

> Perhaps a solution is to make the mail: field more structured:
> 
> mail: 1: name: ""
> mail: 1: email: sm...@example.com
> mail: 2: name: "John Smith"
> mail: 2: email: sm...@foo.com
> mail: 3: name: "Joe Smith"
> mail: 3: email: j...@bar.com
> 
> Which would require even bigger code changes, but might be better
> in the long run.

First of all, this requires an incompatible change of the format of
BBDB records, which I'd like to avoid. Also, I'd like to keep the
user interface as simple as possible.

Roland

--
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/


Re: [BBDB] Changelog 2012-07-31

2012-08-01 Thread Stephen Leake
"Roland Winkler"  writes:

> Part of BBDB (yes, even v2) has allowed the possibility that a mail
> address in a record is not just a plain "sm...@foo.com". But the
> record of, say, Johnathan Smith may also contain an RFC 822 address
> such as "John Smith ". 
>
> Jognathan Smith
>phone (home): (123) 456-7890
>mail: sm...@example.com, John Smith ,
>  Joe Smith 
>
> Obviously, this comes handy, if you want to use different mail
> addresses in a record with different real names. 

With BBDB v2 I always used separate records for this case, putting
(home), (work) etc in the record name, because cycling thru the email
addresses simply did not work properly; it always used the last one.

Now that's fixed, but I suspect I'll still use separate records in a
case like this. For example, sm...@foo.com should have a different work
phone than j...@bar.com. But maybe I need to experiment more.

It would be nice to not have (home) show up in the final
email address; putting a real name in the Mail field could fix that
(assuming it overrides the real name in the record).

> Would it be useful if the canonical mail address "sm...@foo.com"
> contained in full mail address "John Smith " was
> recognized properly throughout BBDB? 

I suspect so, yes.

Perhaps a solution is to make the mail: field more structured:

mail: 1: name: ""
mail: 1: email: sm...@example.com
mail: 2: name: "John Smith"
mail: 2: email: sm...@foo.com
mail: 3: name: "Joe Smith"
mail: 3: email: j...@bar.com

Which would require even bigger code changes, but might be better in the
long run.

-- 
-- Stephe

--
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/


How to merge to records with identical names?

2012-08-01 Thread Alan Schmitt
Hello,

I have a person that was entered twice in bbdb, with the same name but
two different mails. I tried to put the cursor on one of the records and
do a "M-x bbdb-merge-record", but when I enter the second mail address,
I get an error:

Mail address "(the current mail address)" is used by "(the name of the
person)"

I guess I'm doing it wrong, but I don't see how to merge two records. If
someone could give me a hand...

Thanks,

Alan

--
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/


[BBDB] Changelog 2012-07-31

2012-08-01 Thread Roland Winkler
The patch below gives some minor improvements for bbdb-complete-mail.

- Cycle even if the record contains only one mail address, yet
  bbdb-dwim-mail gives us something different from what we have.
  For example, a message header "JOHN SMITH " may be
  replaced by "John Smith ".

- Search correctly for RFC 822 addresses containing a full name.

The latter change revealed another unexpected surprise with BBDB:

Part of BBDB (yes, even v2) has allowed the possibility that a mail
address in a record is not just a plain "sm...@foo.com". But the
record of, say, Johnathan Smith may also contain an RFC 822 address
such as "John Smith ". 

Jognathan Smith
   phone (home): (123) 456-7890
   mail: sm...@example.com, John Smith ,
 Joe Smith 

Obviously, this comes handy, if you want to use different mail
addresses in a record with different real names. But this feature
has been implemented rather incompletely. To make this work
properly, the hash table should always use canonical addresses such
as sm...@foo.com. But currently BBDB puts "John Smith
" in the hash table which makes it really impossible
to find sm...@foo.com in this table. (A hash table does not allow to
search for a regexp.)

Would it be useful if the canonical mail address "sm...@foo.com"
contained in full mail address "John Smith " was
recognized properly throughout BBDB? This will require many calls of
`mail-extract-address-components' upon startup and elsewhere, too. I
do not expect this to become a serious bottleneck. But I'd have to
look through the code a bit more carefully to identify all spots
that need to be changed. Oh well...

2012-07-31  Roland Winkler  
* lisp/bbdb-com.el (bbdb-complete-mail): When a single record
matches, analyze more carefully which mail address to use.  Cycle
even if the record contains only one mail address, yet
bbdb-dwim-mail gives us something different from what we have.
Search correctly for RFC 822 addresses containing a full name.

BBDB is available at
http://savannah.nongnu.org/projects/bbdb/
To check it out, use
git clone git://git.savannah.nongnu.org/bbdb.git

--
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/