emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Martin <kleinerdrache@gmx.at>
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: special table from clock
Date: Thu, 20 Mar 2014 22:56:31 +0100	[thread overview]
Message-ID: <87ob10ilf4.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87a9cm3u88.fsf@gmx.at> (Martin's message of "Wed, 19 Mar 2014	19:43:03 +0100")

Hi Martin,

Martin <kleinerdrache@gmx.at> writes:

> Where do I find the contrib/ repository?

~$ git clone git://orgmode.org/org-mode.git
~$ cd org-mode/contrib/

or http://orgmode.org/org-8.2.5h.zip, unzip, and open the*
contrib/ directory.

> So what I think now is, I'd like to get some elisp functions which can
> parse my orgmode files, where I have i.e. an appointment APPT or an TODO
> entry and getting things (keywords, CLOCK:, properties out of it and
> also the text after my things (or should I the text in a Drawer, maybe
> its easyer for parsers later) - getting the things out of the entries
> and work with them on in any other way.

(org-entry-get (point) "APPT") will get you the value of the property
APPT in the current subtree.  Same for other properties.  As for more
fine-grained parsing, start with (org-element-at-point) -- but beware
this can lead to a long trip into the internals.

You can also check: http://orgmode.org/worg/dev/org-syntax.html,
by Nicolas, which gives a thorough introduction to Org syntax.

> so if org-collector is a good way to see how it works, it would be very
> useful for me.

Please check it and let us know about your progress.

Best,

-- 
 Bastien

      reply	other threads:[~2014-03-20 21:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13 16:25 special table from clock Martin
2014-03-19 11:18 ` Bastien
2014-03-19 18:43   ` Martin
2014-03-20 21:56     ` Bastien [this message]

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=87ob10ilf4.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=kleinerdrache@gmx.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).