(This is in response to Gabriel's message from 1 July. Sorry for the delay)

Gabriel wrote:
another idea: you might want to keep your contacts in a yaml file and then
generate your abook datafiles dynamically
[…]
In this case, you would define different contact groups with your
yaml/perl[WHATEVER OTHER SCRIPTING LANGUAGE] and then dynamically generate the
corresponding abook datafiles.

That would be a very elegant and flexible approach. I am, however, reluctant to write and maintain my own backend like that, for 1) if something breaks, I am on my own then, and 2) I am not very proficient in programming, so coding even something as simple as this is not just a quick side-project for me. (I didn't even get around yet to implement the even simpler solution I proposed a few mails before.)

I did exactly this many years ago and never had to touch my rc files again.
However, somehow I lost track of this.

If you still have your scripts from back then, I would be very interested in having a look at them!

Carlos

Attachment: pgpQG3UD5H91y.pgp
Description: PGP signature

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Abook-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/abook-devel

Reply via email to