emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Michael Käufl" <org-mode@lists.michael-kaeufl.de>
To: Julien Danjou <julien@danjou.info>
Cc: emacs-orgmode@gnu.org, Andrea Crotti <andrea.crotti.0@gmail.com>
Subject: Re: [Org-contacts] 3 2 1 go?
Date: Tue, 08 Mar 2011 22:45:26 +0100	[thread overview]
Message-ID: <8762rt1e2x.fsf@phenom.fritz.box> (raw)
In-Reply-To: <sa3sjuy0ww5.fsf@cigue.easter-eggs.fr> (Julien Danjou's message of "Tue, 08 Mar 2011 10:44:26 +0100")

> For example, some people might want to cut the address part in
> (STREET,ZIPCODE,CITY,COUNTRY) whereas I think it's a burden, I just put
> a LOCATION property with all the address in it. In the end, it does not
> matter for org-contacts.

I use the splitted address version.  And therefore I have one problem
which is however more general. I would like to group some properties.
So that I can have a properties group WORK and another group HOME.


* Friends
** Dave Null
   :PROPERTIES:
   :MOBILE:     +49-1234-456789
   :GROUP-WORK:
     :EMAIL:       dave@work.com
     :LOCATION:    …
     :LANDLINE:    +49-1234-567890
   :GROUP-END:
   :GROUP-HOME:
     :EMAIL:       dave@home.com
     :LOCATION:    …
     :LANDLINE:    +49-1234-987650
   :GROUP-END:
   :END:


I think this is not possible with the current design of the org
properties.  Things like adding to persons /Dave Null (work)/ and
/Dave Null (home)/ or using WORK-EMAIL, HOME-EMAIL, … are not what I
would prefer.

My (at the moment best) idea to support grouping is:


* Friends
** Dave Null
   :PROPERTIES:
   :CONTACT:    t
   :MOBILE:     +49-1234-456789
   :END:
*** work
     :PROPERTIES:
     :EMAIL:       dave@work.com
     :LOCATION:    …
     :LANDLINE:    +49-1234-567890
     :END:
*** home
     :PROPERTIES:
     :EMAIL:       dave@home.com
     :LOCATION:    …
     :LANDLINE:    +49-1234-987650
     :END:


This would use all properties which are set directly as property of the
person as default and all others according to the requested group.

The absence of such groups is imho currently the main difference between
org-contacts and vcard/…


--
Michael

  parent reply	other threads:[~2011-03-08 21:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-05 22:58 [Org-contacts] 3 2 1 go? Andrea Crotti
2011-03-06  2:58 ` Michael Käufl
2011-03-06  7:31   ` Andrea Crotti
2011-03-07 11:25     ` Andrea Crotti
2011-03-07 14:53       ` Julien Danjou
2011-03-07 17:51         ` Re: [O] " Michael Käufl
2011-03-07 11:12 ` Julien Danjou
2011-03-08  9:37   ` Andrea Crotti
2011-03-08  9:44     ` Julien Danjou
2011-03-08  9:57       ` Andrea Crotti
2011-03-08 21:45       ` Michael Käufl [this message]
2011-03-08 22:17   ` Michael Käufl
2011-03-09  8:23     ` Julien Danjou
2011-03-11  8:40       ` Bastien

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=8762rt1e2x.fsf@phenom.fritz.box \
    --to=org-mode@lists.michael-kaeufl.de \
    --cc=andrea.crotti.0@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=julien@danjou.info \
    /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).