From: "Roland Winkler" <winkler@gnu.org>
To: "Barak A. Pearlmutter" <barak@pearlmutter.net>
Cc: George McNinch <gmcninch@gmail.com>,
bbdb <bbdb-info@lists.sourceforge.net>,
emacs-devel@gnu.org
Subject: Re: eudc conversion to bbdb (in bbdb3.1.2?)
Date: Fri, 20 Nov 2015 23:04:07 -0600 [thread overview]
Message-ID: <64327.51692.240507.22095@gargle.gargle.HOWL> (raw)
In-Reply-To: <CANa01BJxhKK3s3DSQU79yM_b4DwoZ428Z3-R+d3iZJruSvRZww@mail.gmail.com>
On Wed Nov 18 2015 Barak A. Pearlmutter wrote:
> But this does bring up a deeper issue, namely exposing a
> documented stable bbdb API might be a good idea.
The question is what kind of scenarios the API is supposed to cover.
I have never thought in much detail about this question.
- This thread started with how EUDC interacts with BBDB. Is there a
list of other packages to be considered here?
- Are we talking about interactive and / or non-interactive
applications interacting with BBDB ("interactive" in the sense of
elisp `interactive')?
- What should an interface look like for searching records in the
database for non-interactive applications? The macro bbdb-search
can possibly be further improved.
- Exporting / importing individual fields for a given record already
has a stable interface via bbdb-record-field and
bbdb-record-set-field.
- Exporting complete records: is bbdb-record-field sufficient for
that purpose?
- Currently there is only little support for importing complete
records (possibly following a previous export). A major issue are
imported records that should be merged with existing records.
Currently BBDB uses elisp `eq' to recognize equal records which is
an approach that can fail in many ways. Adding a UUID field to
every record that gets exported and imported would make this more
robust. (We talked about this before, and it is on my agenda,
though lately my time has been limited.)
- Is there something else?
Roland
next prev parent reply other threads:[~2015-11-21 5:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <82mvuffcyc.fsf@jobim-via-gmail.com>
2015-11-18 17:18 ` eudc conversion to bbdb (in bbdb3.1.2?) Roland Winkler
2015-11-18 20:01 ` Thomas Fitzsimmons
2015-11-21 5:03 ` Roland Winkler
2015-11-21 10:29 ` Adding BBDB 3 core to Emacs (was: eudc conversion to bbdb (in bbdb3.1.2?)) Thomas Fitzsimmons
2015-11-21 16:56 ` Adding BBDB 3 core to Emacs John Wiegley
2015-11-21 17:11 ` Eli Zaretskii
2015-11-21 19:59 ` Thomas Fitzsimmons
2015-11-23 2:03 ` Richard Stallman
2015-11-21 20:02 ` Roland Winkler
2015-11-22 7:02 ` Stephen J. Turnbull
2015-11-22 15:33 ` Roland Winkler
2015-11-22 16:14 ` Stephen J. Turnbull
2015-11-22 21:42 ` Roland Winkler
2015-11-23 1:47 ` Stephen J. Turnbull
2015-11-23 9:04 ` David Kastrup
2015-11-23 2:05 ` Richard Stallman
2015-11-23 3:57 ` Roland Winkler
2015-11-23 16:10 ` Richard Stallman
2015-11-23 18:03 ` Roland Winkler
2015-11-24 2:37 ` Richard Stallman
2015-11-21 19:37 ` Thomas Fitzsimmons
2015-11-21 23:00 ` raman
2015-11-22 5:16 ` John Wiegley
2015-11-21 22:22 ` Roland Winkler
2015-11-18 20:40 ` eudc conversion to bbdb (in bbdb3.1.2?) Barak A. Pearlmutter
2015-11-21 5:04 ` Roland Winkler [this message]
2015-11-21 10:39 ` Barak A. Pearlmutter
2015-11-21 22:55 ` Roland Winkler
2015-11-22 10:14 ` Barak A. Pearlmutter
2015-11-22 21:50 ` Roland Winkler
2015-11-21 13:17 ` Eric Abrahamsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=64327.51692.240507.22095@gargle.gargle.HOWL \
--to=winkler@gnu.org \
--cc=barak@pearlmutter.net \
--cc=bbdb-info@lists.sourceforge.net \
--cc=emacs-devel@gnu.org \
--cc=gmcninch@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.