From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: property searches for #+CATEGORY
Date: Wed, 07 Nov 2007 17:16:26 +0000 [thread overview]
Message-ID: <878x5am0wl.fsf@bzg.ath.cx> (raw)
In-Reply-To: <20071107135235.GM13544@atlantic.linksys.moosehall> (Adam Spiers's message of "Wed, 7 Nov 2007 13:52:35 +0000")
Adam Spiers <orgmode@adamspiers.org> writes:
>> This would let you restrict any agenda search to a group of agenda
>> files. I don't want to digg too far in this direction, but I think
>> there are a few other things for which such groups might be useful
>> (e.g. publish agenda files per group...)
>
> Well, the documentation says
>
> The category is a broad label assigned to each agenda item. By
> default, the category is simply derived from the file name, [...]
>
> so I thought this use case was pretty much exactly what it was
> intended for.
Lets say that #+CATEGORY is more oriented toward files grouping, and
:CATEGORY: is more oriented toward tasks grouping. In fact, when using
several #+CATEGORY in the same file (as it is *not* recommended to do),
you are virtually splitting your file into several files, each of them
corresponding to a category.
Your request was to be able to perform a search using #+CATEGORY as a
way to search through multiple files.
I can see to ways of doing this:
1. implicitely add the #+CATEGORY value of a file to each entry in this
file, and search through files having the same #+CATEGORY;
2. clearly separate the group of files from the group of tasks, and
perform a group-restricted search.
I think (1) is problematic: what if a file has a top #+CATEGORY and
several :CATEGORY: properties? What about precedence and inheritance?
How to build the search string if we want to search through several
:CATEGORY: properties in a single #+CATEGORY ?
> No, I don't think it's #+CATEGORY per se which is only there for
> backward compatibility - it's using it multiple times within a single
> file.
The fact that only *one* instance of #+CATEGORY is allowed in a file
calls itself for the divorce between #+CATEGORY (possibly renamed as
#+GROUP) and the :CATEGORY: property...
>> It's not that easy for users to understand how to user categories,
>> and staying with two ways of setting them might be confusing IMO.
>
> Surely this is an argument against introducing yet another grouping
> mechanism! We already have tags, properties, and categories.
But a category is just a property, even if the search interface raises
this property above others. And besides these search considerations, I
really believe that having several groups of agenda-files would help.
> I already have too many problems keeping a good work/life balance! ;-)
Com'on, our daily brain-sport is to feed this list! :)
--
Bastien
next prev parent reply other threads:[~2007-11-07 16:16 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 [this message]
2007-11-07 17:23 ` Adam Spiers
2007-11-08 4:42 ` Bastien
2007-11-07 16:20 ` Carsten Dominik
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=878x5am0wl.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).