From: Michael Brand <michael.ch.brand@gmail.com>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: Matt Lundin <mdl@imapmail.org>, emacs-orgmode@gnu.org
Subject: Re: Occurance property, or some similar name?
Date: Wed, 13 Apr 2011 17:42:19 +0200 [thread overview]
Message-ID: <BANLkTikGc0h_o8d4GyJj6aeTgEaaXpzqAQ@mail.gmail.com> (raw)
In-Reply-To: <87oc4aky8m.fsf@dustycloud.org>
On Wed, Apr 13, 2011 at 16:43, Christopher Allan Webber
<cwebber@dustycloud.org> wrote:
> Michael Brand <michael.ch.brand@gmail.com> writes:
>> * _appointment_ that _occurs_ at bike shop (keyword inside drawer)
>> :PROPERTIES:
>> :TIMESTAMP: <2011-04-12 Tue 19:00>
>> :END:
>> * _appointment_ that _occurs_ at bike shop (keyword outside drawer)
>> :TIMESTAMP: <2011-04-12 Tue 19:00>
>> * _appointment_ that _occurs_ at bike shop (keyword-less, at least for
>> backward compatibility)
>> <2011-04-12 Tue 19:00>
>
> Interesting, I like that style. My main concern is that newer orgmode
> files written in this form might break in older versions of orgmode.
Are your concerns concrete?
I have thought about and tested this already before: The three example
items above show up in the agenda, and are still correct even after
changing with `S->'. So this "newer/future" Org file format works even
with the "older/today" Org software. This is because the Org software
of today flexibly binds the special property TIMESTAMP per item to the
first active timestamp (i. e. "<>", not "[]") that is not prefixed
with `SCHEDULED: ' or `DEADLINE: '. This binding is the reason why I
would stick to the name TIMESTAMP when it comes to possibly new
features that should write this special property keyword explicitly
for this kind of timestamp. The sibling (not `C-c .') of `C-c
C-s'/`C-c C-d' that you suggested originally would be such a feature.
Michael
next prev parent reply other threads:[~2011-04-13 15:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 22:42 Occurance property, or some similar name? Christopher Allan Webber
2011-04-12 4:22 ` theo
2011-04-12 14:41 ` Christopher Allan Webber
2011-04-12 19:28 ` Matt Lundin
2011-04-12 19:25 ` Matt Lundin
2011-04-12 20:52 ` Christopher Allan Webber
2011-04-13 1:01 ` Matt Lundin
2011-04-13 13:07 ` Christopher Allan Webber
2011-04-13 8:19 ` Michael Brand
2011-04-13 13:08 ` Christopher Allan Webber
2011-04-13 14:19 ` Michael Brand
2011-04-13 14:43 ` Christopher Allan Webber
2011-04-13 15:42 ` Michael Brand [this message]
2011-04-13 15:57 ` Christopher Allan Webber
2011-04-12 20:00 ` Memnon Anon
2011-04-12 20:24 ` Richard Riley
2011-04-13 15:34 ` Carsten Dominik
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=BANLkTikGc0h_o8d4GyJj6aeTgEaaXpzqAQ@mail.gmail.com \
--to=michael.ch.brand@gmail.com \
--cc=cwebber@dustycloud.org \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.org \
/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).