On Sat Mar 22 2014 Sriram Karra wrote:
> Agreed. The alist should take a field name - can be one of the
> standard field names, or a user defined notes field key and value
> being can either be a set of defined symbols (like merge,
> keep-older, keep-newer) or if it's a function it will be invoked
On Sat, Mar 22, 2014 at 10:34 PM, Roland Winkler wrote:
[...]
> For example, there could be a user variable bbdb-merge-field-alist
> that defines recipes for each field how to merge them when merging
> records.
Agreed. The alist should take a field name - can be one of the standard
field name
On Sat Mar 22 2014 Sriram Karra wrote:
> When I merge two records in BBDB is there some way I can control
> what happens to specific fields.
Currently the command bbdb-merge-records is what it is (with not
much customization). But I guess it can be extended in many ways,
including some customizat
When I merge two records in BBDB is there some way I can control what
happens to specific fields. For e.g. for records that synced to an external
datastore I maintain an ID as part of the record itself. When two such
records are merged I want one of them to be dropped and only one retained.
Is the
