From: "Eddward DeVilla" <eddward@gmail.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: Duration Tally
Date: Tue, 19 Jun 2007 11:20:38 -0500 [thread overview]
Message-ID: <b71b18520706190920x5c719907rdf15903f1d2ea94e@mail.gmail.com> (raw)
In-Reply-To: <ad8e80bfef52d434a21c479dee42455f@science.uva.nl>
On 6/19/07, Carsten Dominik <dominik@science.uva.nl> wrote:
>
> 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.
I don't expect to see any of this soon or in this form. It just
idea I've been trying to justify bringing up. Where I'd want to use
it most is in custom agenda queries. "Show me projects(todos) that
are associated with release X of product Y. Release and Product would
be my keywords.
Right now all we have is a TODO state and a list of tags. Tags
are basically boolean. You have to have a tag for each thing you want
to report on. A tag for every product ID, a tag for every release
identifier, tags for interested parties, tags for classes, etc. And
all the tags are mixed together in a long run-on string at the end of
the heading. It can get unreadable.
I also would like to be able to set a property like this that I
can then use in tables under the TODO item. I'd have other uses for
that, but I'd like to set the property in the same way. This isn't as
useful, but I've wished for it more than once. Just a way to set a
variable in an org document that I can then use in formula.
Originally I thought it would be a '#' directive but I do like this as
a possible way to do it.
While playing with these ideas and reading the message that
trigger all of this, I thought it would be nice to be able to code an
extension that would allow me to insert a keyword like TOTAL_DURATION:
that would automatically (based on some trigger) be assigned a value
equal to the sum of all the DURATION: values under the current TODO
item. I know the original request sounded useful, but it seem very
non-general and it was yet another thing to clutter the heading.
The property list would give us easy access to user/plugin
definable/managed fields. I think we would want a way to hook into a
few other org-isms, like having an easy way to say C-cC-c or C-uC-cC-c
makes something happen here. But this is all still wild fantasy of
the bizarre and possibly impractical. I was hoping it might bring
about a better idea.
Edd
next prev parent reply other threads:[~2007-06-19 16:20 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
2007-06-19 11:24 ` Russell Adams
2007-06-19 16:20 ` Eddward DeVilla [this message]
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=b71b18520706190920x5c719907rdf15903f1d2ea94e@mail.gmail.com \
--to=eddward@gmail.com \
--cc=dominik@science.uva.nl \
--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).