emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: coroa@online.de (Jonas Hörsch)
To: emacs-orgmode@gnu.org
Subject: org-element.el doesn't support interpreting repeating range timestamps
Date: Thu, 10 Jan 2013 13:11:14 +0100	[thread overview]
Message-ID: <87txqpjl0d.fsf@online.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 249 bytes --]


i just noticed, that although org-element properly parses the repeating
information of an active-range :type timestamp, it is not able to
interpret it again (unless the :raw-value is still present, of course).

minimal working example below:

[-- Attachment #2: mwe.org --]
[-- Type: text/x-org, Size: 865 bytes --]

* ❢ Tagesschau
<2013-01-15 Tue 20:00 +1d>--<2013-01-15 Tue 20:15 +1d>

* Parsing
#+name: timestamp
#+begin_src emacs-lisp
  (org-element-map (org-element-parse-buffer) 'timestamp 'identity nil t)
  :parent nil)   ; so we don't clutter the output uselessly
 :raw-value nil) ; with raw-value it works, trivially

#+RESULTS: timestamp
| timestamp | (:type active-range :raw-value nil :year-start 2013 :month-start 1 :day-start 15 :hour-start 20 :minute-start 0 :year-end 2013 :month-end 1 :day-end 15 :hour-end 20 :minute-end 15 :begin 17 :end 71 :post-blank 0 :repeater-type cumulate :repeater-value 1 :repeater-unit day :parent nil) |

* Interpreting
#+begin_src emacs-lisp :var elem=timestamp
(org-element-interpret-data elem)

: <2013-01-15 Tue 20:00>--<2013-01-15 Tue 20:15>

[-- Attachment #3: Type: text/plain, Size: 15 bytes --]


             reply	other threads:[~2013-01-10 12:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 12:11 Jonas Hörsch [this message]
2013-01-10 13:11 ` org-element.el doesn't support interpreting repeating range timestamps Nicolas Goaziou

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:

  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=87txqpjl0d.fsf@online.de \
    --to=coroa@online.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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).