Richard G Riley <[EMAIL PROTECTED]> writes:
> When I get a work process sorted out then I will try and produce my own
> small "tutorial" while it is fresh in my mind along with links back to
> the relevant online documentation.
That would be great, thanks!
--
Bastien
_
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)
Richard G Riley <[EMAIL PROTECTED]> writes:
> Yes. I see them. I am confused with this Read/NEXT value. Is this the
> tag or is Read the tag? What should the line look like in my org file
> e.g I have:
Please *read* this:
http://orgmode.org/org.html#Tag-searches
Read is the tag, NEXT is a to
Richard G Riley <[EMAIL PROTECTED]> writes:
>> (setq org-agenda-custom-commands
>> '(("r" tags-todo "Read/NEXT" nil)
>> ("w" tags-todo "Write/NEXT" nil)
>> ("R" tags-todo "Read/NEXT|TODO" nil)
>> ("W" tags-todo "Write/NEXT|INPROGRESS" nil)))
>
> Where do you press "r"
Richard G Riley <[EMAIL PROTECTED]> writes:
>>> There is no "properties_alL" which determine which properties you can
>>> add.
>>
>> Not relevant here, because there is no reason why the user would like to
>> limit the set of available properties.
>
> Must disagree. Completion doesn't *limit* the
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.
>
>> ,
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 (
| (
tags/categories :VOCAB:
SCHEDULED: <2007-10-14 Sun> DEADLINE: <2007-10-15 Mon>
:PROPERTIES:
:CATEGORY: Emacs
:MISC: test
:END:
[2007-10-12 Fri]
[[gnus:nnmaildir%2BMyMail:DevelopmentEmail#886][Email from Bastien:
Re: Orgm
On Oct 12, 2007, at 17:04, Richard G Riley wrote:
Yes. The concept of not having to worry about where things are in the
org file doesn't really work for me. I like things having a certain
category in that category section - otherwise there seems little point
in having lines like
,
| * Emac
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
Carsten Dominik <[EMAIL PROTECTED]> writes:
> You can add a category property to the entry, and that will overrule the
> category that might be inherited from above. With the latest org-mode
> 5.12,
> press `C-c C-x p'. This will prompt you for a property name, enter
> CATEGORY
> (using completi
: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 the task above to another
category
nice and easily and not using cut and paste? Is it p
erty? In this case that is what I have -
sections of tasks with a category section separating them. e.g
,
| * FaceBook
|
| :PROPERTIES:
| :CATEGORY: FaceBook
| :END:
|
|
| * Emacs
|
| :PROPERTIES:
| :CATEGORY: Emacs
| :END:
|
| ** [2007-10-12 Fri 15:03] How to use categories in org-mo
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.
>> ,
Richard G Riley <[EMAIL PROTECTED]> writes:
>> You could set a :CATEGORY: property for entry.
>>
> How do you do that?
Please check (info "(Org)Property syntax") to know more about
properties.
> | #+CATEGORY: Emacs
Although this is still supported, you can now use this:
,
| * A headline h
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: Reg
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" t
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?
The patch did the trick, and I now see the need for the different
inheritance behaviors.
Thanks,
Dan
--
** TODO Learn Emacs Lisp
Carsten Dominik wrote:
> Hi Daniel
>
> On May 24, 2006, at 22:21, Daniel J. Sinder wrote:
>
>>
>> I've recently encountered one bug and one inconsistency (I'm up to
Hi Daniel
On May 24, 2006, at 22:21, Daniel J. Sinder wrote:
I've recently encountered one bug and one inconsistency (I'm up to
date with 4.33).
Here's the bug: After generating the first weekly agenda and
quitting it, subsequent tag-search agendas result in the same
CATEGORY label on all ent
I'm using org-mode for GTD, and I also use tags for GTD context. I
put TODO entries under headlines for their respective projects and
use a tag for each project which is inherited by it's next
actions/TODOs. I have 3 main org files for GTD: work, meetings,
personal -- each with #+CATEGORY labels
22 matches
Mail list logo
