Richard G Riley [EMAIL PROTECTED] writes:
Aha ok. Note that like a lot of things its easy when you know how.
Well, my post started with this:
,
| My setting for tags is this:
|
| #+TAGS: { Read(r) Write(w) Code(c) }
| #+TAGS: Mail(m) Print(p)
| #+TAGS: { @HOME(H) @LAB(L) }
On Oct 13, 2007, at 14:22, Richard G Riley wrote:
Carsten Dominik [EMAIL PROTECTED] writes:
On Oct 12, 2007, at 19:20, Richard G Riley wrote:
I have a possible bug here (5.12). When embedding the CATEGORY as a
property e.g in my org file
Yes, logging state changes is broken in 5.12,
Carsten Dominik [EMAIL PROTECTED] writes:
On Oct 12, 2007, at 19:20, Richard G Riley wrote:
I have a possible bug here (5.12). When embedding the CATEGORY as a
property e.g in my org file
Yes, logging state changes is broken in 5.12, *#$*#$.
Fixed in 5.12c, thanks.
,
|
Hi,
Eddward DeVilla [EMAIL PROTECTED] writes:
You could set a :CATEGORY: property for entry.
Edd
This is different from a tag how?
How do you do that?
At the moment my org file has sections like this:
,
| * Emacs
|
| #+CATEGORY: Emacs
|
|
| * Register
|
| #+CATEGORY: Register
]
[[gnus:nnmaildir%2BMyMail:DevelopmentEmail#886][Email from Bastien:
Re: Orgmode Categories]]
when I change the state e.g with this custom command sample
,
| '(org-agenda-custom-commands
|(quote (
| (d org-todo DELEGATED nil)
|(c org-todo DONE|DEFERRED|CANCELLED nil
On Oct 12, 2007, at 19:20, Richard G Riley wrote:
I have a possible bug here (5.12). When embedding the CATEGORY as a
property e.g in my org file
Yes, logging state changes is broken in 5.12, *#$*#$.
Fixed in 5.12c, thanks.
,
| '(org-agenda-custom-commands
|(quote (
| (d
Richard G Riley [EMAIL PROTECTED] writes:
Completion doesnt work for me. Possibly this is a result of using
icicles? You just TAB to completion?
Can you please provide more details:
What version of Org-mode?
What did you do?
What did you expect?
What did you get instead?
This might seem
Richard G Riley [EMAIL PROTECTED] 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.
,
|
: FaceBook
| :END:
|
|
| * Emacs
|
| :PROPERTIES:
| :CATEGORY: Emacs
| :END:
|
| ** [2007-10-12 Fri 15:03] How to use categories in org-mode
|
| [[gnus:nnmaildir%2BMyMail:DevelopmentEmail#874][Email from Bastien: Re:
Orgmode Categories]]
`
My original question is how to assign
,
| * FaceBook
|
| :PROPERTIES:
| :CATEGORY: FaceBook
| :END:
|
|
| * Emacs
|
| :PROPERTIES:
| :CATEGORY: Emacs
| :END:
|
| ** [2007-10-12 Fri 15:03] How to use categories in org-mode
|
| [[gnus:nnmaildir%2BMyMail:DevelopmentEmail#874][Email from
Bastien: Re: Orgmode Categories]]
`
My
Categories are fairly handy for keeping the agenda well organised, but
what are the functionalities for moving tasks between different
categories e.g a task might move from PROJ1 to PROJ2 or some
such? Must it be done manually using cut and paste in the org file?
You could set a :CATEGORY: property for entry.
Edd
On 10/11/07, Richard G Riley [EMAIL PROTECTED] wrote:
Categories are fairly handy for keeping the agenda well organised, but
what are the functionalities for moving tasks between different
categories e.g a task might move from PROJ1 to PROJ2
12 matches
Mail list logo
