From: Bastien <bastien.guerry@wikimedia.fr>
To: Skip Collins <skip.collins@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: properties in agenda prefix
Date: Wed, 18 Aug 2010 16:43:36 +0200 [thread overview]
Message-ID: <87k4nnzvs6.fsf@altern.org> (raw)
In-Reply-To: <AANLkTikU1KAxUZ1B7BuoUiKvH1gwfgk9+ak+2qsqzG7i@mail.gmail.com> (Skip Collins's message of "Wed, 18 Aug 2010 08:03:54 -0400")
Hi,
Skip Collins <skip.collins@gmail.com> writes:
>> What property would you find useful to have and why?
>
> CUSTOM_ID could be handy right away. If arbitrary properties were
> accessible in agenda prefix, it would enable very flexible agenda
> constructs. Consider a setup in which headlines are given a tracking
> number that can be used as a reference number outside of org. The
> reference number would naturally be a property, not a tag. To get a
> nice list that includes the reference number, it must be assigned to
> CATEGORY.
>
> Consider also a group agenda in which items are flagged in the prefix
> with the names of their owners. Again, the names must now be assigned
> to CATEGORY.
Yes, I agree `org-agenda-prefix-format' could use a more general syntax,
e.g. allow user-defined properties.
> As a design goal, I think would it make sense for agenda and column
> modes to have some overlapping features and syntax, including the
> ability to access properties.
I grasp the general idea but a more concrete use-case would help here
again... thanks!
--
Bastien
next prev parent reply other threads:[~2010-08-18 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 3:28 properties in agenda prefix Skip Collins
2010-08-18 6:24 ` Carsten Dominik
2010-08-18 9:39 ` Bastien
2010-08-18 12:03 ` Skip Collins
2010-08-18 14:43 ` Bastien [this message]
2010-08-18 22:45 ` Skip Collins
2010-08-18 23:15 ` Nick Dokos
2010-08-19 6:46 ` Jan Böcker
2010-08-24 18:32 ` Skip Collins
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=87k4nnzvs6.fsf@altern.org \
--to=bastien.guerry@wikimedia.fr \
--cc=emacs-orgmode@gnu.org \
--cc=skip.collins@gmail.com \
/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).