From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bastien <bzg@altern.org>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: property searches for #+CATEGORY
Date: Wed, 7 Nov 2007 17:20:32 +0100 [thread overview]
Message-ID: <DE719112-3EF8-4F25-A7DB-30362C8B71F7@science.uva.nl> (raw)
In-Reply-To: <871wb2p2f9.fsf@bzg.ath.cx>
On 7Nov2007, at 3:15 PM, Bastien wrote:
>
> I understand now.
>
> I think it would be clearer to distinguish between categorizing files
> and categorizing tasks. In a sense, using #+CATEGORY across several
> files (as you do) is more a way to group these files under the same
> ombrella (conveniently called "category"), rather than to group all
> tasks below each #+CATEGORY in the same category.
>
> Let me say it with other words: if several files share the same
> #+CATEGORY, then this bit of information won't be of any help to
> distinguish between these files' tasks, it will only help separating
> files with #+CATEGORY: A from files with #+CATEGORY: B.
>
> Then I think the right solution would be to have groups of agenda
> files.
> Something like:
>
> #+AGENDA_GROUP: personal
The idea to have groups of agenda files has come up before.
It is hard to implement because agenda creating commands
are *global* commands, so the group should not be a property
of the location from where you call the agenda.
You can, of course, already make custom commands that are
restricted to a specific group of files, by setting
`org-agenda-files' as one of the options for a custom command
in org-agenda-custom-comands....
- Carsten
next prev parent reply other threads:[~2007-11-07 17:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 11:17 property searches for #+CATEGORY Adam Spiers
2007-11-07 12:49 ` Bastien
2007-11-07 12:15 ` Adam Spiers
2007-11-07 13:23 ` Tim O'Callaghan
2007-11-07 13:34 ` Adam Spiers
2007-11-07 13:59 ` Tim O'Callaghan
2007-11-07 14:28 ` Adam Spiers
2007-11-07 14:52 ` Tim O'Callaghan
2007-11-07 16:35 ` Adam Spiers
2007-11-07 16:15 ` Carsten Dominik
2007-11-07 18:07 ` Adam Spiers
2007-11-08 4:55 ` Bastien
2007-11-08 8:54 ` Carsten Dominik
2007-11-07 14:49 ` Bastien
2007-11-07 14:32 ` Adam Spiers
2007-11-07 14:15 ` Bastien
2007-11-07 13:52 ` Adam Spiers
2007-11-07 17:16 ` Bastien
2007-11-07 17:23 ` Adam Spiers
2007-11-08 4:42 ` Bastien
2007-11-07 16:20 ` Carsten Dominik [this message]
2007-11-08 0:04 ` Adam Spiers
-- strict thread matches above, loose matches on Subject: below --
2008-12-07 23:35 Mario E. Munich
2008-12-08 16:40 ` Carsten Dominik
2008-12-09 0:33 ` Mario E. Munich
2008-12-09 1:41 ` Matthew Lundin
2008-12-09 6:51 ` Mario E. Munich
2008-12-07 23:39 Mario E. Munich
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=DE719112-3EF8-4F25-A7DB-30362C8B71F7@science.uva.nl \
--to=carsten.dominik@gmail.com \
--cc=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).