From: Eric Abrahamsen <firstname.lastname@example.org> To: emacs-orgmode <email@example.com> Subject: Re: Contact data and sync revisited Date: Sun, 31 May 2020 10:31:49 -0700 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <20200531123018.GD23478@volibear> (Russell Adams's message of "Sun, 31 May 2020 14:30:18 +0200") Russell Adams <RLAdams@AdamsInfoServ.Com> writes: > I've been trying to find the best way to manage my contacts. I've dabbled with > org-contact and using an Org file with property drawers, I've dabbled with > BBDB. I've looked at standalone programs. > > My key problem is I need a way to access my contacts in Emacs and Mutt, and send > them to my Android phone. Single direction sync is fine. > > Using a Nextcloud host, org-caldav, and DAVx5 I have already successfully pushed my > calendar events to my Android phone. This makes it even more important for me to > solve this issue finally. > > I've considered the merit of a few options: > > - Use Org-contacts > - Pro: It's in org! So easy, lets me keep notes and appointment data easily. > - Cons: Doesn't export at all. > > - BBDB > - Pro: It's in Emacs natively, with Org integration. > - Pro: Larger users base than Org-contacts, more software > - Cons: Exports but requires additional tools to sync > > Unfortunately looking at the options keeps coming back to how poor general > support for CardDAV and vcard files is. In particular, the popular vdirsyncer > tool is now looking for a new maintainer, and I had the impression from his list > of grievances he might drop it entirely. This is not yet a working solution, but I'm gradually getting there with EBDB, a port/rewrite of BBDB. It does vCard export, though not very well yet. I've also written a library called "vcard", which does parsing of vcards into Elisp data, but have yet to get off my butt and wire everything together. The end result will be an EBDB database that uses the vCard format natively for storage. Then I was planning on relying on vdirsyncer for CardDAV syncing, and it's a bummer to hear that it might go unmaintained. I could write a native CardDAV client using dav.el, but seeing how much fun David Engster has maintaining org-caldav, I'm not eager to go that route. If you're interested, you can follow this issue. https://github.com/girzel/ebdb/issues/4 Yes, it's issue #4, opened in 2016. Don't let that discourage you! Eric
next prev parent reply other threads:[~2020-05-31 17:32 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-31 12:30 Russell Adams 2020-05-31 16:18 ` Matthew Lundin 2020-05-31 17:31 ` Eric Abrahamsen [this message] 2020-05-31 20:52 ` rey-coyrehourcq 2020-05-31 21:23 ` Russell Adams 2020-05-31 17:49 ` Bob Newell 2020-05-31 19:16 ` Russell Adams
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Contact data and sync revisited' \ /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
Code repositories for project(s) associated with this 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).