From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Re: PATCH: include in-progress/started todos into daily agenda
Date: Thu, 27 Sep 2007 22:49:53 +0200 [thread overview]
Message-ID: <87tzpfvnny.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87ps04droy.wl%max@openchat.com> (Max Mikhanosha's message of "Thu, 27 Sep 2007 12:00:13 -0400")
Max Mikhanosha <max@openchat.com> writes:
> Seeing "INPROGRESS Finish coding feature X" instead does not
> discourage me as I don't have to be reminded that I had already wasted
> 2 weeks on it, it just reminds me to continue to work on it today.
I get this point.
The only problem I can see with the solution you're proposing is this:
how do you know that a INPROGRESS headline is of the "sticky" kind? How
do you distinguish between those "keep-motivation-up" headings and other
INPROGRESS headings that are scheduled for this date?
Maybe you just don't *want* to distinguish between them, but other
people might at least expect some visual clue.
As for the vertical space limitation, I guess this wouldn't hurt that
much to get rid of the blank line and of the "========" line. And if you
want your INPROGRESS tasks to be displayed first, just swap the order of
(agenda) and (todo "INPROGRESS") in org-agenda-custom-commands?
--
Bastien
next prev parent reply other threads:[~2007-09-27 20:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 20:50 PATCH: include in-progress/started todos into daily agenda Max Mikhanosha
2007-09-27 1:33 ` Carsten Dominik
2007-09-27 14:33 ` Max Mikhanosha
2007-09-27 15:18 ` Carsten Dominik
2007-09-27 16:00 ` Max Mikhanosha
2007-09-27 20:49 ` Bastien [this message]
2007-10-09 16:09 ` Carsten Dominik
2007-10-09 19:18 ` Max Mikhanosha
2007-10-09 20:52 ` Bastien
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=87tzpfvnny.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
/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).