On Fri Sep 30 2011 Eric Abrahamsen wrote: > 1. If there's no value for a field, you get a nice ugly "nil". Ideally > we'd have conditional insertion of strings depending on whether or > not there's a value for a given field, but that means we can't use > `format' anymore, and suddenly this whole thing gets a *lot* more > complicated than a Friday afternoon project.
This reminds me of BBDB address via bbdb-address-format-list. One needs to keep track of everything... > 2. There's no obvious way of indicating which value of a multi-valued > field you want. `bbdb-record-get-field' only gets us so far, as it's > indiscriminate about fields with string values, list values and > struct values. Currently I am trying to make bbdb-record-get-field a bit more flexible as this had also popped up here in some other context. I want to install my patch in the near future. Yet this might not solve all your problems. (See my comments on string labels below.) > With a little work it would be possible to access subvalues by > constructing complex field names: for instance, address-home > (to get the address field labelled "home") Note that "home" may appear multiple times (i.e., the string labels used for addresses and phone numbers) > I've seen people mess with symbol names like this before, and > could probably figure it out. The keys of note fields (which are symbols) are intended to be unique for each record. Roland ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/