"T. V. Raman" <[EMAIL PROTECTED]> writes:
> Could we perhaps introduce a special property that is used by
> org-agenda to build the left column?
What about:
:PROPERTIES:
:CATEGORY: general
:ARCHIVE: archives::
:END:
as a future replacement for #+CATEGORY and
On Sep 6, 2007, at 7:34, Bastien wrote:
"T. V. Raman" <[EMAIL PROTECTED]> writes:
Could we perhaps introduce a special property that is used by
org-agenda to build the left column?
What about:
:PROPERTIES:
:CATEGORY: general
:ARCHIVE: archives::
:END:
as a future replacement for #
That would get some level of consistency in which sounds like a
good idea.
> "Bastien" == Bastien <[EMAIL PROTECTED]> writes:
Bastien> "T. V. Raman" <[EMAIL PROTECTED]> writes:
>> Could we perhaps introduce a special property that is used
>> by org-agenda to build the left colum
"T. V. Raman" <[EMAIL PROTECTED]> writes:
> Could we perhaps introduce a special property that is used by
> org-agenda to build the left column?
What about:
:PROPERTIES:
:CATEGORY: general
:ARCHIVE: archives::
:END:
as a future replacement for #+CATEGORY and #+ARCHIVE?
--
Bastien
__
I'm perfectly happy to do this with properties rather than
categories. But I suggested categories because that is what
agenda views are using at present in the left column.
Could we perhaps introduce a special property that is used by
org-agenda to build the left column?
> "Carsten" == Carste
Yes, a minor thing, fixed now.
- Carsten
On Sep 5, 2007, at 7:19, Bastien wrote:
Carsten Dominik <[EMAIL PROTECTED]> writes:
it will be okay to set
whatever property you want through the column view -- and perhaps the
column view itself would be available in the agenda ebuffer
it is!
Arg
Carsten Dominik <[EMAIL PROTECTED]> writes:
>> it will be okay to set
>> whatever property you want through the column view -- and perhaps the
>> column view itself would be available in the agenda ebuffer
>
> it is!
Argh... I didn't even give it a try, shame on me. But now that I boldly
did, C-
On Sep 4, 2007, at 20:00, Bastien wrote:
"T. V. Raman" <[EMAIL PROTECTED]> writes:
It would be nice to have an interactive org-agenda-set-category
alongside org-agenda-set-tag in the agenda buffer.
I think it doesn't make sense to have `org-agenda-set-category' until
we
are able to set th
Putting it immediately after the headline is how I would
implement it.
And it would work depending on ones workstyle --- most features
of org make sense only in the context of a work style.
> "Bastien" == Bastien <[EMAIL PROTECTED]> writes:
Bastien> "T. V. Raman" <[EMAIL PROTECTED]> wri
It would be nice to have an interactive org-agenda-set-category
alongside org-agenda-set-tag
in the agenda buffer.
+1
Later, it might also be nice to implement a function that say
rearranges all todo entries of a particular category under a
common section. I find myself doin
"T. V. Raman" <[EMAIL PROTECTED]> writes:
> It would be nice to have an interactive org-agenda-set-category
> alongside org-agenda-set-tag in the agenda buffer.
I think it doesn't make sense to have `org-agenda-set-category' until we
are able to set the category as a property of the headline.
Fo
It would be nice to have an interactive org-agenda-set-category
alongside org-agenda-set-tag
in the agenda buffer.
This would allow one to quickly categorize tasks.
Later, it might also be nice to implement a function that say
rearranges all todo entries of a particular category under a
common
12 matches
Mail list logo
