From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Re: Allowing loose ordering in Org files
Date: Wed, 11 Nov 2015 17:13:25 +0100 [thread overview]
Message-ID: <2015-11-11T16-40-39@devnull.Karl-Voit.at> (raw)
In-Reply-To: m27flp398d.fsf@Vulcan.attlocal.net
* John Wiegley <jwiegley@gmail.com> wrote:
>
> In my regimen, every single entry has a PROPERTIES drawer, since I tag each
> one with ID and CREATED, for future reference.
This also holds for my Org-mode files - in general.
> Most items are SCHEDULED as well. So when I open up a headline to
> look at the contents, I see:
>
> * Head
> SCHEDULED
> text
> :PROPERTIES:...
>
> It's a trivial thing, but I'd rather not scan past two lines to start reading
> my entry.
I just wanted to add an additional notion to the discussion:
In most cases, the content of the drawers gets populated
automatically (LOGBOOK, CREATED, ...). In some cases, I manually add
properties, mainly :ID: for being able to use references to it.
Below the drawers, there is the actual content which is free text,
mixed with lists, blocks, and so forth.
In those cases, I prefer drawers being closed by default.
However, in my contacts.org file, I have entries where the actual
content is in a rather strict form like:
,----
| ** Firstname Lastname :FirstnameLastname:
| :PROPERTIES:
| :TYPE: person
| :TITLE:
| :EMAIL: Firstname.Lastname@example.com
| :URL: http://example.com
| :MOBILE: 0043/123456789
| :HOMEPHONE:
| :WORKPHONE:
| :PHONE:
| :COMPANY:
| :STREET: Herrengasse 42
| :POSTALCODE: 8042
| :CITY: Graz
| :COUNTRY: Österreich
| :PHOTOGRAPH: [[photo:FirstnameLastname.jpg]]
| :BORN: 1970-12-31
| :ITOLDTHEM_EMAIL: Lastname@MYDOMAIN.at
| :ITOLDTHEM_ADDRESS: home
| :ITOLDTHEM_PHONE: mobile
| :ADDRESS_CHANGE_METHOD: email
| :CREATED: [2015-11-11 Wed 16:51]
| :END:
|
| - first contact: <2015-11-11 Wed> when meeting at id:FooConf15
`----
Here, the drawer is of particular interest to me and I'd love to
have them expanded together with the heading.
Besides, I once started an attempt to define a standard for contact
property item names in order to enable external tools to parse
contact data like [1]. Unfortunately, my focus shifted and I did not
follow my standardization attempt much further:
http://thread.gmane.org/gmane.emacs.orgmode/45347/focus=45740
http://thread.gmane.org/gmane.emacs.orgmode/47434/focus=47490
http://article.gmane.org/gmane.emacs.orgmode/57231/
[...]
Two notions: first, content of properties are of different interest
for different people in different org-mode files with different
data. It's hard to derive a general rule here.
Second, I still do think that a bit more standardization would be a
benefit for Org-mode (contact data, order of org elements, ...).
Having written a pretty dumb Org-mode parser in Python by myself for
[2] I recognized that this is not an easy job to do properly outside
of Elisp. And: being able to use Org-mode files outside of
Emacs/Elisp is also of interest for all users of Emacs/Elisp.
Just my 2 cents.
[1] https://github.com/novoid/org-contacts2vcard
[2] https://github.com/novoid/lazyblorg
--
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
> get Memacs from https://github.com/novoid/Memacs <
https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
next prev parent reply other threads:[~2015-11-11 16:13 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 0:11 bug in org-habits Mark A. Hershberger
2015-11-03 9:56 ` Marco Wahl
2015-11-03 11:16 ` Puneeth Chaganti
2015-11-03 13:11 ` John Wiegley
2015-11-03 13:46 ` Marco Wahl
2015-11-03 14:20 ` Stelian Iancu
2015-11-03 16:31 ` Nicolas Goaziou
2015-11-03 19:20 ` John Wiegley
2015-11-03 19:35 ` Nicolas Goaziou
2015-11-03 20:17 ` John Wiegley
2015-11-03 20:52 ` Nicolas Goaziou
2015-11-03 20:55 ` John Wiegley
2015-11-03 21:31 ` Achim Gratz
2015-11-03 21:36 ` John Wiegley
2015-11-03 21:48 ` Jonathan Leech-Pepin
2015-11-03 21:56 ` John Wiegley
2015-11-03 22:36 ` Achim Gratz
2015-11-03 22:45 ` John Wiegley
2015-11-04 13:01 ` Bastien Guerry
2015-11-04 20:26 ` John Wiegley
2015-11-09 15:13 ` Allowing loose ordering in Org files (Was: bug in org-habits) John Wiegley
2015-11-09 17:47 ` Allowing loose ordering in Org files Rasmus
2015-11-09 18:15 ` John Wiegley
2015-11-09 19:28 ` Rasmus
2015-11-09 19:57 ` John Wiegley
2015-11-09 19:12 ` Achim Gratz
2015-11-09 19:24 ` John Wiegley
2015-11-09 20:04 ` Achim Gratz
2015-11-09 21:13 ` Stelian Iancu
2015-11-09 21:30 ` John Wiegley
2015-11-10 1:40 ` Allowing loose ordering in Org files (Was: bug in org-habits) Aaron Ecay
2015-11-10 1:52 ` Allowing loose ordering in Org files John Wiegley
2015-11-10 5:31 ` Thomas S. Dye
2015-11-10 17:37 ` Nicolas Goaziou
2015-11-10 19:20 ` Thomas S. Dye
2015-11-10 20:02 ` John Wiegley
2015-11-10 20:42 ` Matt Lundin
2015-11-10 20:44 ` Matt Lundin
2015-11-10 17:51 ` Matt Lundin
2015-11-10 18:19 ` Matt Lundin
2015-11-10 19:49 ` Achim Gratz
2015-11-10 20:11 ` John Wiegley
2015-11-10 20:38 ` Achim Gratz
2015-11-10 22:35 ` John Wiegley
2015-11-11 16:13 ` Karl Voit [this message]
2015-11-10 11:30 ` Allowing loose ordering in Org files (Was: bug in org-habits) Stelian Iancu
2015-11-03 23:43 ` bug in org-habits Nicolas Goaziou
2015-11-04 1:01 ` John Wiegley
2015-11-04 9:02 ` Stelian Iancu
2015-11-04 9:16 ` Eric S Fraga
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=2015-11-11T16-40-39@devnull.Karl-Voit.at \
--to=devnull@karl-voit.at \
--cc=emacs-orgmode@gnu.org \
--cc=news1142@Karl-Voit.at \
/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).