From: John Hendy <jw.hendy@gmail.com>
To: Olivier Schwander <olivier.schwander@chadok.info>
Cc: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>, emacs-orgmode@gnu.org
Subject: Re: indenting nested TODOs in agenda views
Date: Mon, 22 Aug 2011 09:06:20 -0500 [thread overview]
Message-ID: <CA+M2ft_zcbzfQhmqZYzPpuTxcoJPtGFVPp4ZXWWp+XhAeU2M2w@mail.gmail.com> (raw)
In-Reply-To: <20110822135011.GA19319@bugaga.lan>
On Mon, Aug 22, 2011 at 8:50 AM, Olivier Schwander
<olivier.schwander@chadok.info> wrote:
> Yes, I was looking for the same kind of thing some times ago. But I do
> not have any idea of how we may present the agenda view. Maybe it should
> be better do display the path to a TODO item, since parent item may be
> not TODO items by themselves, like this:
>
> * Garden
> ** TODO Cut the flowers
> * Home
> ** TODO Cut the flowers
>
> should be presented somehow like in the refile view, as:
>
> TODO Garden / Cut the flowers
> TODO Home / Cut the flowers
>
> instead of the unclear:
>
> TODO Cut the flowers
> TODO Cut the flowers
>
> Actually, I wonder how people deals with this kind of tasks. Are you
> relying on tags ? For example with :garden: and :home: in my previous
> example ?
>
I *just* corresponded with the list about something like this within
the last month or two, but can't find the thread. The response I got
back was that the person relied on adding descriptive words to all the
todos, which is what I've been doing, but I don't like it. I host a
lot of external vendors at work and have the same structure for all of
them:
----------
* proj [/] host vendor x
** todo set date
** todo book room
** todo request abstract
** todo submit event announcement
** todo post presentation online
----------
They're so similar that I can just copy/yank the subtree from one to
the other... but then I have to go change each to:
----------
** todo x: set date
----------
and so on. Time consuming and non-ideal. It would be great to know
what the subtask belongs to for things like this. When I have two
vendors within a week or two, it gets confusing.
JOhn
> Personally, I am used to recall the main heading at the beginning of the
> children, but only when the TODO item heading is really not clear enough
> by itself, since it is a quite heavy solution.
>
>> Just an incentive to tell you I'd also would love that feature.
>
> Same :)
>
> Best,
>
> Olivier
>
>
>
next prev parent reply other threads:[~2011-08-22 14:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 11:16 indenting nested TODOs in agenda views Eric Abrahamsen
2011-08-22 11:37 ` Bernt Hansen
2011-08-22 11:56 ` Eric Abrahamsen
2011-08-22 12:26 ` Sebastien Vauban
2011-08-22 13:50 ` Olivier Schwander
2011-08-22 14:02 ` Jason Dunsmore
2011-08-22 14:06 ` John Hendy [this message]
2011-08-22 14:24 ` Sebastien Vauban
2011-08-22 16:29 ` Achim Gratz
2011-08-23 9:10 ` Eric Abrahamsen
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=CA+M2ft_zcbzfQhmqZYzPpuTxcoJPtGFVPp4ZXWWp+XhAeU2M2w@mail.gmail.com \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=olivier.schwander@chadok.info \
--cc=wxhgmqzgwmuf@spammotel.com \
/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).