On Tue, May 19, 2009 at 05:01, Manish mailtomanish.sha...@gmail.com wrote:
Of course, I do not know elisp nor do I understand Org internals so
the idea might just be nonsense from an implementation perspective.
Nonsense or not I like the idea a lot!
It would be of great help to me.
Wow, didn't think this observation would generate so much buzz :) Great to
know other org-mode users feel the need for it too.
Another aspect is that when you archive and item (when it's DONE) it's nice
to know it's context. If you have a NEXT ACTION that belongs to a project
and this specific NA
My wording!
You seem to have found a comrade.
I would further suggest getting in touch (apart from the mailing list and
exchanging ideas and current setup).
On Tue, May 19, 2009 at 23:27, Marcelo de Moraes Serpa
celose...@gmail.comwrote:
Wow, didn't think this observation would generate so much
Hi Marcelo,
Marcelo de Moraes Serpa celose...@gmail.com writes:
Another aspect is that when you archive and item (when it's DONE) it's
nice to know it's context. If you have a NEXT ACTION that belongs to a
project and this specific NA is already DONE, if you archive it you'll
loose context.
On Wed, May 20, 2009 at 00:29, Matthew Lundin m...@imapmail.org wrote:
Org-mode already can save context info as properties. See the variable
org-archive-save-context-info.
I do not have this variable (Org-Version:6.26trans).
Eraldo
___
Eraldo,
Good to know that! I definetly would like to get in touch with you with more
time to discuss it. Meanwhile, Carsten (or any other org-savvy developer)
could point us into the right direction on which is the best way to start
hacking org (towards makeing extensions for it).
I have many,
Eraldo Helal ad...@eraldo.at wrote:
On Wed, May 20, 2009 at 00:29, Matthew Lundin m...@imapmail.org wrote:
Org-mode already can save context info as properties. See the variable
org-archive-save-context-info.
I do not have this variable (Org-Version:6.26trans).
You probably need to
On Wed, May 20, 2009 at 2:57 AM, Marcelo de Moraes Serpa wrote:
Wow, didn't think this observation would generate so much buzz :) Great to
know other org-mode users feel the need for it too.
Another aspect is that when you archive and item (when it's DONE) it's nice
to know it's context. If
On May 20, 2009, at 1:06 AM, Marcelo de Moraes Serpa wrote:
Eraldo,
Good to know that! I definetly would like to get in touch with you
with more time to discuss it. Meanwhile, Carsten (or any other org-
savvy developer) could point us into the right direction on which is
the best way to
On Mon, May 18, 2009 at 04:07, Matthew Lundin m...@imapmail.org wrote:
In my opinion, the easiest way to figure out which project a TODO
belongs to is to use follow mode in the agenda. That way you can see the
original context (i.e., project) to which a todo belongs.
This works great for
The follow-mode works fine, and this is what I use currently, but usually
the item doesn't have data that tells clearly what it's parent item is. It'd
be nice to have this overview, in the flat form -- like Eraldo said, if
you'd like to print or just have a 10.000 feet view of the actions.
I'm
I recall that there was a variable that controls whether dots get put
into the agenda line to show that it is a child of the previous agenda
line, or something like that.
Might possibly work if you include the parent?
What was the name of that variable anyway?
On Sun, May 17, 2009 at 19:07,
No, just a workaround of inserting both the parent and the child and
letting the dots tell you the relationship between them.
But perhaps I am not following the thread closely enough.
On Mon, May 18, 2009 at 15:01, Eraldo Helal ad...@eraldo.at wrote:
On Mon, May 18, 2009 at 18:21, Samuel Wales
On Tue, May 19, 2009 at 00:16, Samuel Wales samolog...@gmail.com wrote:
No, just a workaround of inserting both the parent and the child and
letting the dots tell you the relationship between them.
How?
I would have to show all Project headlines in order to make this work...
However, I only
I had the idea of using CATEGORY as a keyword.
Benefit:
using #+CATEGORY (or the CATEGORY property)
has the disadvantage that if I change the headline the category does not
update:
example:
Org-file:
* PROJECT *my_renamed_project1*
:PROPERTIES:
:CATEGORY: *myproject1*
:END:
** TODO clean
On Sat, May 16, 2009 at 8:41 PM, Carsten Dominik wrote:
On May 15, 2009, at 11:33 PM, Marcelo de Moraes Serpa wrote:
Hello list,
I'd like to do a little modification to the code that grabs the
summary of items for the agenda view. For each item that has a
parent with a
I am having a similar problem as Marcelo...
However, in order to keep the agenda flat I only want the parent PROJECT
headline (the inner most) to be the prefix.
In his example this would be the following:
My-sub-sub-project *NEXT Call Liz RE: account creation *
:@call:@work:
The
Eraldo Helal ad...@eraldo.at writes:
I am having a similar problem as Marcelo...
However, in order to keep the agenda flat I only want the parent
PROJECT headline (the inner most) to be the prefix.
In his example this would be the following:
My-sub-sub-project NEXT Call Liz RE: account
On Sun, May 17, 2009 at 23:25, Matthew Lundin m...@imapmail.org wrote:
Why not use categories for this? You could define a category for each
project:
--8---cut here---start-8---
** Some Project
:PROPERTIES:
:CATEGORY: special project
:END:
***
Eraldo Helal ad...@eraldo.at writes:
On Sun, May 17, 2009 at 23:25, Matthew Lundin m...@imapmail.org wrote:
Why not use categories for this? You could define a category for
each
project:
--8---cut here---start-8---
** Some
On May 15, 2009, at 11:33 PM, Marcelo de Moraes Serpa wrote:
Hello list,
I'd like to do a little modification to the code that grabs the
summary of items for the agenda view. For each item that has a
parent with a PROJECT type, I'd like org to render this parent in a
hierarchical, tree
21 matches
Mail list logo
