emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: exported contacts problem
Date: Sat, 3 Aug 2019 12:33:40 +0200	[thread overview]
Message-ID: <20190803103340.GN23820@protected.rcdrun.com> (raw)
In-Reply-To: <875znfaycd.fsf@ericabrahamsen.net>

* Eric Abrahamsen <eric@ericabrahamsen.net> [2019-08-03 02:27]:
> Okay, thanks for that run-down, pretty interesting. I've written a
> package called EBDB[1] that's meant to be sort of an update to BBDB, and
> while I think someone's using it with tens of thousands of contacts,
> 192k records would probably exhaust it. It has pluggable data stores,
> however, one of which will (eventually) be a proper external database,
> so I'm always interested in how people are using this stuff.
> 
> Eric
> 
> [1] https://github.com/girzel/ebdb

I have tried it. It has good concepts and integration. But I cannot
switch to it.

Please, if you intend to make vcard import, don't make vcard stuff
bundled with the ebdb, you will make repeated mistake.

Make one vcard import package that give elisp structure, something
like hash or alist, plist, whatever is better.

Then such package is best to contribute to GNU Emacs.

Then all other packages can use vcard import.

This makes much sense rather than making it single-package oriented.

I don't think that vCard complexity is necessary for contacts,
standard is invented, but is too complex. But if you are doing it,
than such feature can contribute to overall usage.

Jean

  reply	other threads:[~2019-08-03 10:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 15:47 exported contacts problem Jude DaShiell
2019-08-02 16:00 ` Jean Louis
2019-08-02 16:02 ` Jean Louis
2019-08-02 16:06   ` Jude DaShiell
2019-08-02 21:09   ` Eric Abrahamsen
2019-08-02 21:34     ` Jean Louis
2019-08-03  0:26       ` Eric Abrahamsen
2019-08-03 10:33         ` Jean Louis [this message]
2019-08-03 15:38           ` Eric Abrahamsen
2019-08-03 16:32             ` Jean Louis
2019-08-03 17:48               ` Neil Jerram
2019-08-03 18:25                 ` Jean Louis
2019-08-03 21:32                 ` Eric Abrahamsen
2019-08-03 22:12                   ` Jean Louis
2019-08-04  1:28                   ` Tim Cross
2019-08-13 22:24                   ` David Masterson
2019-08-14 20:38                     ` Eric Abrahamsen
2019-08-16  0:07                       ` David Masterson
2019-08-03 10:48         ` Jean Louis
2019-08-02 22:19   ` John Kitchin
2019-08-02 20:33 ` Tim Cross
2019-08-02 20:57   ` Jude DaShiell
2019-08-02 21:25     ` Tim Cross
2019-08-02 21:39       ` Jean Louis
2019-08-02 22:07         ` Tim Cross
2019-08-03  8:25           ` Jean Louis
2019-08-02 21:00   ` Jean Louis

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190803103340.GN23820@protected.rcdrun.com \
    --to=bugs@gnu.support \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric@ericabrahamsen.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).