From: Xebar Saram <zeltakc@gmail.com>
To: Alexis <flexibeast@gmail.com>, org mode <emacs-orgmode@gnu.org>
Subject: Re: org-contacts development
Date: Sat, 24 May 2014 07:02:42 +0300 [thread overview]
Message-ID: <CAOQHXPqdD+fFGdB0-CuJqzxA4m2TnGO6bUkHj-yo6mMLLi7fEQ@mail.gmail.com> (raw)
In-Reply-To: <87vbswu6re.fsf@mailbox.org>
[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]
Hi Alexis
This sounds awesome, i would love syncing org contacts with my android phone
thx alot!
z
On Fri, May 23, 2014 at 1:30 PM, Alexander Baier <
alexander.baier@mailbox.org> wrote:
> Hello Alexis,
>
> On 2014-05-23 06:07 Alexis wrote:
>
> [...]
>
> > What would be useful would be an 'official', fleshed-out spec for
> > org-contacts data, which handles a greater range of contact-related
> > info. At the moment, for example, my org-contacts file makes use of the
> > properties:
> >
> > #+PROPERTY: LANDLINE
> > #+PROPERTY: MOBILE
> > #+PROPERTY: POST
> > #+PROPERTY: RESIDENCE
> >
>
> [...]
>
> > Fleshing out an extended spec for org-contacts data could be part of the
> > process of making org-contacts a first-class citizen of org-mode, and
> > provide a more solid foundation on which people can build (and share)
> > the org-contacts functionality they're after. And in my own particular
> > case, it would greatly facilitate my work in org-contacts / Android
> > Contacts integration. :-)
> >
> > What do people think?
>
> I, for one, would love to see org-contacts being improved in any way.
> Integrating this with MobileOrg would be an extremely helpful and
> something I have wanted since the day I started using org-contacts.
>
> About the spec, might it make sense to use a standard already in
> existence as a starting point or even a major inspiration? Something
> like vCard for example?
>
> Regards,
> --
> Alexander Baier
>
>
[-- Attachment #2: Type: text/html, Size: 2129 bytes --]
next prev parent reply other threads:[~2014-05-24 4:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 4:07 org-contacts development Alexis
2014-05-23 9:06 ` Rasmus
2014-05-23 10:30 ` Alexander Baier
2014-05-24 4:02 ` Xebar Saram [this message]
2014-05-24 10:27 ` Alexis
2014-05-24 10:15 ` Alexis
2014-05-24 14:18 ` Alexander Baier
2014-05-24 14:55 ` Bastien
2014-05-24 15:05 ` Alexis
2014-05-24 15:43 ` Rasmus
2014-05-24 16:10 ` Alexis
2014-05-23 12:45 ` Bastien
2014-05-23 15:46 ` Rasmus
2014-05-24 10:04 ` Alexis
2014-05-24 12:17 ` Bastien
2014-05-24 14:07 ` Alexis
2014-05-24 9:00 ` Org-contacts standardization (was: org-contacts development) Karl Voit
[not found] ` <878ups27km.fsf@gmx.us>
2014-05-24 9:59 ` org-contacts development Alexis
2014-05-24 16:51 ` Daimrod
2014-05-24 17:48 ` Alexis
2014-05-26 3:21 ` Daimrod
2014-05-26 4:06 ` Alexis
2014-05-26 15:20 ` Michael Strey
2014-05-27 9:27 ` Michael Strey
2014-05-29 3:19 ` Daimrod
2014-06-03 10:23 ` Michael Strey
2014-06-05 4:26 ` Daimrod
2014-07-23 13:40 ` Karl Voit
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=CAOQHXPqdD+fFGdB0-CuJqzxA4m2TnGO6bUkHj-yo6mMLLi7fEQ@mail.gmail.com \
--to=zeltakc@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=flexibeast@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 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).