On Mon Oct 3 2011 Eric Abrahamsen wrote:
> Okay, it sounds like this is different enough to warrant me waiting on
> it. In the meantime, if you have any clever ideas about the string
> format/templating side of things, don't be shy!
...maybe not a bad idea. Indeed, my patch has grown more than I h
On Sun, Oct 02 2011, Roland Winkler wrote:
> On Sun Oct 2 2011 Eric Abrahamsen wrote:
>> Can you drop any hints about how it will change? Extra arguments?
>
> I didn't want to do anything fancy. Yet if the field argument
> doesn't match anything what it is supposed to match now, the new
> code als
On Sun Oct 2 2011 Roland Winkler wrote:
> So if the value of field is 'note, it returns a list of all note
> fields. If the value is 'notes, it returns the value of the 'notes
> field.
Of course this is confusing - it should be the other way round:
`notes' should represent all note fields, and `no
On Sun Oct 2 2011 Eric Abrahamsen wrote:
> Can you drop any hints about how it will change? Extra arguments?
I didn't want to do anything fancy. Yet if the field argument
doesn't match anything what it is supposed to match now, the new
code also tries to match the keys of individual note fields. S
On Sun, Oct 02 2011, Roland Winkler wrote:
> 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 c
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
On Mon, Sep 26 2011, Roland Winkler wrote:
> On Mon Sep 26 2011 Eric Abrahamsen wrote:
>> While we're on the subject of features that won't be considered until
>> version 3 is finished, if ever
>>
>> I've been writing a small function to export BBDB records according to
>> an arbitrary text temp
On Mon Sep 26 2011 Leo wrote:
> (nickname () "jvm")
> (phone ((type "home")) "01223 399255")
> (phone ((type "cell")) "07899 825396")
>
> (timestamp ((value list)) (20096 21292 563816))
> (timestamp ((value string)) "Mon Sep 26 18:26:13 2011")
>
> (photo ((value binary)) "%\211Do^\DXlY\2005^H")
On 2011-09-26 17:50 +0800, Roland Winkler wrote:
> On Mon Sep 26 2011 Leo wrote:
>> It might be desirable to export a record to a canonical sexp then we can
>> further write the sexp to any other formats such as vcards, xmls etc.
>> For example, the sexp can be a list of elements of the form:
>>
>
On Mon Sep 26 2011 Leo wrote:
> It might be desirable to export a record to a canonical sexp then we can
> further write the sexp to any other formats such as vcards, xmls etc.
> For example, the sexp can be a list of elements of the form:
>
> (field parameters value)
Maybe you can explain in
On Mon, Sep 26 2011, Roland Winkler wrote:
> On Mon Sep 26 2011 Eric Abrahamsen wrote:
>> While we're on the subject of features that won't be considered until
>> version 3 is finished, if ever
>>
>> I've been writing a small function to export BBDB records according to
>> an arbitrary text temp
It might be desirable to export a record to a canonical sexp then we can
further write the sexp to any other formats such as vcards, xmls etc.
For example, the sexp can be a list of elements of the form:
(field parameters value)
Leo
--
On Mon Sep 26 2011 Roland Winkler wrote:
> > Also, does this seem like a good idea in general? I know that we're in
> > some kind of feature freeze, but this would also be relatively distinct
> > from the rest of the codebase, and if it's an attractive idea I'd be
> > happy to chew on it in my spar
On Mon Sep 26 2011 Eric Abrahamsen wrote:
> While we're on the subject of features that won't be considered until
> version 3 is finished, if ever
>
> I've been writing a small function to export BBDB records according to
> an arbitrary text template. I'm running up against the problem that
> the
14 matches
Mail list logo
