emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: property searches for #+CATEGORY
Date: Thu, 08 Nov 2007 04:42:25 +0000	[thread overview]
Message-ID: <87ode5l55a.fsf@bzg.ath.cx> (raw)
In-Reply-To: <20071107172302.GR13544@atlantic.linksys.moosehall> (Adam Spiers's message of "Wed, 7 Nov 2007 17:23:02 +0000")

Hi Adam,

Adam Spiers <orgmode@adamspiers.org> writes:

> Again, at risk of being pedantic I would describe my requirement
> slightly differently.  (N.B. I can already search through multiple
> files.)

Thanks for the very clear & interesting explanations.

> In fact, the only thing missing is that the code for doing a
> property-based tag search doesn't honour #+CATEGORY, only CATEGORY
> properties.

Right.  Now I understand it would be consistent to include #+CATEGORY in
the category *search*.  I was mainly choking on what Carsten mentionned
in his reply about whether org-entry-get should return the category as
defined by #+CATEGORY -- I guess this is the only consistency-hole.

But since where are speaking about search interface, this is not a
problem, that's right.

> Firstly categories present the user with another interface to learn
> about.  I am certainly not complaining, but you cannot discount the
> extra complexity they introduce, and therefore we should be careful
> about introducing yet more complexity.  

I didn't want to add complexity, but rather expressivity.

My line of reasoning was this one:

1. it is not recommended to use #+CATEGORY twice in a file

2. then the main use of #+CATEGORY will be for grouping *files*

3. if we use #+CATEGORY for grouping files (or tasks across files) and
   :CATEGORY: for grouping tasks, let's separate these two mechanismes
   more clearly

4. this would spare us the cost of deciding what value `org-entry-get'
   should return when asked for the category, in case a file uses both
   #+CATEGORY and :CATEGORY:...

But again, this line depends on how fussy we are about (4) and search
considerations ask for flexibility -- not fussiness :)

>> And besides these search considerations, I really believe that
>> having several groups of agenda-files would help.
>
> Quite possibly, though probably not for me :-) Can you suggest a use
> case or two?

It's mainly for publishing: for now I have to put each project in each
directory so that `org-publish-project-alist' DTRT.  I'd rather publish
groups of files, thus being able to quickly decide what file is in what
group.

> Argh, way too much time spent on this list today ;-)

:)

-- 
Bastien

  reply	other threads:[~2007-11-08  3:42 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 [this message]
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=87ode5l55a.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).