emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Categories
Date: Fri, 12 Oct 2007 15:56:45 +0100	[thread overview]
Message-ID: <877ils8jpu.fsf@bzg.ath.cx> (raw)
In-Reply-To: <fgy7e85vf3.fsf@home.net> (Richard G. Riley's message of "Fri, 12 Oct 2007 15:12:16 +0200")

Richard G Riley <rileyrgdev@googlemail.com> writes:

>> The CATEGORY property does the same job than the old #+CATEGORY, except
>> that its scope is well defined, i.e. we don't need to bother anymore on
>> where #+CATEGORY has to be.
>
> Did you before? 

IIRC this was a recurrent issue on this list.

>> ,----
>> | (setq org-remember-templates
>> |       '((?c "* %?\n   :PROPERTIES:\n   :CATEGORY: %^{Category}\n   :END:\n\n  %i\n" "~/org/todo.org" "Tasks")))
>> `----
>
> Almost. There is no completion or "pick" for the available categories. I
> would expect something like a "tab for completion" field similar to set
> tag for a task.

Yes.  We can imagine something like %^c (prompt for a category with
proper completion).  But then why not %^s for the SUMMARY property?  
And %^d for the DESCRIPTION property?  My answer try to avoid going 
into this, since I (still) think handling properties from within a
remember template is a bit too much.  But I might be wrong.

>> Inserting properties (including the CATEGORY property) interactively
>> from a template looks a bit too much for me.  But not using remember
>> very often, and only for taking quick notes -- not editing my main 
>> Org file.
>
> I'm not sure I understand. One of the most important task properties is
> the category I would have though.

You can use property inheritance.  Ask your remember template to put the
entry in the right subtree, and use a category for that entry only. 

Isn't this more simple?

-- 
Bastien

  parent reply	other threads:[~2007-10-12 13:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11 23:05 Categories Richard G Riley
2007-10-12  3:16 ` Categories Eddward DeVilla
2007-10-12  9:00   ` Categories Richard G Riley
2007-10-12 13:31     ` Categories Bastien
     [not found]       ` <fgy7e85vf3.fsf@home.net>
2007-10-12 14:56         ` Bastien [this message]
2007-10-12 14:12           ` Categories Richard G Riley
2007-10-12 14:27             ` Categories Carsten Dominik
2007-10-12 15:04               ` Categories Richard G Riley
2007-10-12 17:00                 ` Categories Bastien
     [not found]                   ` <qfr6k0b8f8.fsf@home.net>
     [not found]                     ` <87bqb4uri3.fsf@bzg.ath.cx>
     [not found]                       ` <ml641cb5wj.fsf@home.net>
     [not found]                         ` <87r6k0tboe.fsf@bzg.ath.cx>
     [not found]                           ` <0sprzk9pcu.fsf@home.net>
     [not found]                             ` <87641cdniz.fsf@bzg.ath.cx>
     [not found]                               ` <uzk5prdwxm.fsf@home.net>
     [not found]                                 ` <87tzovjeer.fsf@bzg.ath.cx>
     [not found]                                   ` <13k5prcg2a.fsf@home.net>
     [not found]                                     ` <87bqb3jcsm.fsf@bzg.ath.cx>
     [not found]                                       ` <77zlykith7.fsf@home.net>
2007-10-15 11:32                                         ` Categories Bastien
     [not found]                   ` <jnr6jwtk1o.fsf@home.net>
2007-10-15 17:54                     ` Categories Bastien
     [not found]                       ` <t1lka4thoz.fsf@home.net>
2007-10-15 18:38                         ` Categories Bastien
     [not found]                           ` <jbhcksjmnx.fsf@home.net>
2007-10-15 18:57                             ` Categories Bastien
     [not found]                               ` <2yd4vgdyxe.fsf@home.net>
2007-10-15 19:24                                 ` Categories Bastien
2007-10-12 17:07                 ` Categories Carsten Dominik
2007-10-12 17:20                   ` Categories Richard G Riley
2007-10-12 18:20                     ` Categories Carsten Dominik
2007-10-13 12:22                       ` Categories Richard G Riley
2007-10-14  6:14                         ` Categories Carsten Dominik

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=877ils8jpu.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).