* Org-contacts and where to store address
@ 2011-08-06 16:40 Karl Voit
2011-08-17 10:32 ` Bastien
0 siblings, 1 reply; 3+ messages in thread
From: Karl Voit @ 2011-08-06 16:40 UTC (permalink / raw)
To: emacs-orgmode
Hi!
I am writing an Python-script that converts my old jPilot contact
information to Org-mode. I chose Org-contacts[1] because it seems to
me that this will be a widely used format.
In my old format, the address field is a multi-line field similar
to:
,----[ example ]
| Street Name 42
| 0815 City
| Country
`----
I am using property values for EMAIL, HOMEPHONE, WORKPHONE, PHONE,
MOBILE, FAX, TITLE, and COMPANY.
Is there a good way of adding the (multi line) address to the
PROPERTY drawer or should I put the address in the notes right below
the drawers?
PS: Empty properties are not mentioned in the Org-mode manual. Do
they cause any trouble? (I was thinking of leaving empty properties
for each entry so that I can easily add e.g. a FAX number later on
...)
1. http://julien.danjou.info/org-contacts.html
--
Karl Voit
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Org-contacts and where to store address
2011-08-06 16:40 Org-contacts and where to store address Karl Voit
@ 2011-08-17 10:32 ` Bastien
2011-08-17 16:26 ` Karl Voit
0 siblings, 1 reply; 3+ messages in thread
From: Bastien @ 2011-08-17 10:32 UTC (permalink / raw)
To: news1142; +Cc: emacs-orgmode
Hi Karl,
Karl Voit <devnull@Karl-Voit.at> writes:
> I am writing an Python-script that converts my old jPilot contact
> information to Org-mode. I chose Org-contacts[1] because it seems to
> me that this will be a widely used format.
>
> In my old format, the address field is a multi-line field similar
> to:
>
> ,----[ example ]
> | Street Name 42
> | 0815 City
> | Country
> `----
>
> I am using property values for EMAIL, HOMEPHONE, WORKPHONE, PHONE,
> MOBILE, FAX, TITLE, and COMPANY.
>
> Is there a good way of adding the (multi line) address to the
> PROPERTY drawer or should I put the address in the notes right below
> the drawers?
I'd suggest reformatting the multi-lines address into a single-line
string.
> PS: Empty properties are not mentioned in the Org-mode manual. Do
> they cause any trouble?
Not that I'm aware of.
Thanks for letting us know about your progress!
Best,
--
Bastien
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Org-contacts and where to store address
2011-08-17 10:32 ` Bastien
@ 2011-08-17 16:26 ` Karl Voit
0 siblings, 0 replies; 3+ messages in thread
From: Karl Voit @ 2011-08-17 16:26 UTC (permalink / raw)
To: emacs-orgmode
* Bastien <bzg@altern.org> wrote:
> Hi Karl,
Hi!
> Karl Voit <devnull@Karl-Voit.at> writes:
>
>> Is there a good way of adding the (multi line) address to the
>> PROPERTY drawer or should I put the address in the notes right below
>> the drawers?
>
> I'd suggest reformatting the multi-lines address into a single-line
> string.
Done that. The original data was in fact not multi-line and so I
modified the source code to get one line per information.
> Thanks for letting us know about your progress!
Well, it is pretty simple:
contacts.org with two main headings: one for people and one for
companies with one person in yasnippet-syntax:
,----[ yasnippet template for one contact ]
| # name : Org-contacts template for a person
| # --
| ** $1 $2 :$1$2:
| :PROPERTIES:
| :TYPE: ${3:$$(yas/choose-value '("person" "company"))}
| :TITLE:
| :EMAIL: $4
| :MOBILE: ++43/
| :HOMEPHONE:
| :WORKPHONE:
| :PHONE:
| :COMPANY:
| :STREET:
| :POSTALCODE:
| :CITY:
| :COUNTRY: Österreich
| :END:
|
| Erstkontakt: $0
|
|
`----
--
Karl Voit
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-08-17 16:26 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-08-06 16:40 Org-contacts and where to store address Karl Voit
2011-08-17 10:32 ` Bastien
2011-08-17 16:26 ` Karl Voit
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).