From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Feature Request: org-agenda-set-category
Date: Tue, 04 Sep 2007 20:00:13 +0200 [thread overview]
Message-ID: <877in6e2fm.fsf@bzg.ath.cx> (raw)
In-Reply-To: <18141.23318.769156.930384@gargle.gargle.HOWL> (T. V. Raman's message of "Tue, 4 Sep 2007 06:18:14 -0700")
"T. V. Raman" <raman@users.sf.net> writes:
> It would be nice to have an interactive org-agenda-set-category
> alongside org-agenda-set-tag in the agenda buffer.
I think it doesn't make sense to have `org-agenda-set-category' until we
are able to set the category as a property of the headline.
For now categories (like the archiving locations) are set by looking
*backward* for a line like #+CATEGORY or #+ARCHIVE.
When setting the category with `org-agenda-set-category', where should
such a line be inserted/modified? Just above the headline? Then storing
this headline won't delete the #+CATEGORY line. Just under the headline?
Then the headline itself won't be recognized as belonging to that
category... See the discussion here:
http://article.gmane.org/gmane.emacs.orgmode/2898
Please anybody stops me if I'm wrong, but I guess the #+ARCHIVE and
#+CATEGORY instructions are slowly dying and will be set as properties
in the future. We already (as of 5.07) have these new properties when
archiving:
:ARCHIVE_TIME: 2007-09-01 sam 05:54
:ARCHIVE_FILE: ~/org/bzg.org
:ARCHIVE_CATEGORY: nothot
Then, in the new world, where such #+CONSTRUCTS are only used to set
*file* properties (not headlines properties), it will be okay to set
whatever property you want through the column view -- and perhaps the
column view itself would be available in the agenda ebuffer, which
would let you have your `org-agenda-set-category'.
(Of course #+CATEGORY will remain, but only as a way to categorize
files, not headlines.)
> This would allow one to quickly categorize tasks.
Yes, as the column view allows quick selection of *any* property.
> Later, it might also be nice to implement a function that say
> rearranges all todo entries of a particular category under a common
> section. I find myself doing this by hand at present, and Emacs will
> probably do it better than my fingers.
Maybe `org-sort-entries' could group entries that have a property in
common.
--
Bastien
next prev parent reply other threads:[~2007-09-04 18:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 13:18 Feature Request: org-agenda-set-category T. V. Raman
2007-09-04 18:00 ` Bastien [this message]
2007-09-05 2:16 ` T. V. Raman
2007-09-05 3:40 ` Carsten Dominik
2007-09-05 5:19 ` Bastien
2007-09-05 6:08 ` Carsten Dominik
2007-09-06 3:43 ` T. V. Raman
2007-09-06 5:34 ` Bastien
2007-09-06 13:25 ` T. V. Raman
2007-09-07 8:04 ` Carsten Dominik
2007-09-09 14:21 ` Nuutti Kotivuori
2007-09-13 5:44 ` Carsten Dominik
2007-09-10 1:00 ` Xavier Maillard
2007-09-06 9:25 ` Christian Egli
2007-09-05 1:00 ` Xavier Maillard
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=877in6e2fm.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--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).