From: Carsten Dominik <dominik@science.uva.nl>
To: Eddward DeVilla <eddward@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Duration Tally
Date: Tue, 19 Jun 2007 09:00:19 +0200 [thread overview]
Message-ID: <ad8e80bfef52d434a21c479dee42455f@science.uva.nl> (raw)
In-Reply-To: <b71b18520706130833r8714029jb59a8b21084b2223@mail.gmail.com>
On Jun 13, 2007, at 17:33, Eddward DeVilla wrote:
> I'm starting to wonder if it would be useful to have a general
> format for properties (or choose some other word) to be associated
> with a heading or todo item. It seems the heading is getting a little
> crowded.
>
> Would it be reasonable to say that a list of non-whitespace
> listing following the heading with a format of "key: value..." are
> special. (Or a table might be nice. I like tables.:) org-mode could
> provide an interface to get a plist or alist of them for a heading to
> simplify writing now features based on them.
One of the advantages of using plain text for notes files like
we do with Org-mode is, that you can of course implement any system
you like to store additional information. Keyword lists, tables,
anything.
So the discussion must be about how you would like Org-mode to make
use of such data. Obviously it would be easy to write (as you
suggest) a little function that returns all this data as, say,
a property list. But then you would still need to use it in
some way. Are you suggesting tis as a feature where some users
(those who can write Lisp code) write their own extensions?
That is certainly an option. Are you also envisioning ways
how Org-mode should use this?
Here are tow ideas:
- a LOCATION keyword would be useful for exporting to iCalendar,
this was already proposed by Bastien a while ago.
- We could allow the TAGS match to set conditions based on these
keywords. Right now, a tags match can say "LEVEL=2" to require
entries with putline level 2. In a similar way one could allow
"LOCATION=Paris" or whatever, that would be something quite
easily implemented.
Nothing of this will be in todays release, obviously, this needs
more careful thinking. Thanks for starting this discussion.
- Carsten
next prev parent reply other threads:[~2007-06-19 7:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 13:47 Duration Tally Russell Adams
2007-06-13 15:33 ` Eddward DeVilla
2007-06-14 2:15 ` Russell Adams
2007-06-14 13:28 ` Jason F. McBrayer
2007-06-19 7:00 ` Carsten Dominik [this message]
2007-06-19 11:24 ` Russell Adams
2007-06-19 16:20 ` Eddward DeVilla
2007-06-19 17:45 ` Scott Jaderholm
2007-06-19 18:28 ` Eddward DeVilla
2007-06-22 15:56 ` Carsten Dominik
2007-06-22 19:06 ` Scott Jaderholm
2007-06-22 19:35 ` Eddward DeVilla
2007-06-13 21:58 ` Scott Jaderholm
[not found] ` <b71b18520706131837m42b32f5cs174d94c2b353d16d@mail.gmail.com>
2007-06-15 0:13 ` Fwd: " Eddward DeVilla
2007-06-15 6:21 ` Carsten Dominik
2007-06-19 2:16 ` Russell Adams
2007-06-19 7:02 ` Carsten Dominik
2007-06-19 11:21 ` Russell Adams
2007-06-19 13:10 ` Carsten Dominik
2007-06-19 17:12 ` Russell Adams
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=ad8e80bfef52d434a21c479dee42455f@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=eddward@gmail.com \
--cc=emacs-orgmode@gnu.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).