From: Bernt Hansen <bernt@norang.ca>
To: Jean-Marie Gaillourdet <jmg@gaillourdet.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Not a bug, but ...
Date: Sun, 27 Jun 2010 08:21:13 -0400 [thread overview]
Message-ID: <87y6e0d5ty.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <7B46216F-526B-448A-9518-31F0034C496B@gaillourdet.net> (Jean-Marie Gaillourdet's message of "Sun\, 27 Jun 2010 11\:41\:01 +0200")
Jean-Marie Gaillourdet <jmg@gaillourdet.net> writes:
> Finally, I've understood the problem. Testprojekt does not appear on
> my stuck projects list, because I've enabled
> org-enforce-todo-dependencies and I use (org-agenda-dim-blocked-tasks
> 'invisible). Testprojekt is just hidden in the stuck projects, as is
> every project with any kind of non-closed sub task. Perhaps
> org-agenda-list-stuck-projects should ignore the value of
> org-agenda-dim-blocked-tasks in general?
>
> Currently, I use the following function to circumvent the hiding of my
> stuck projects.
>
> (defun jmg/stuck-projects ()
> (interactive)
> (let ((org-agenda-dim-blocked-tasks nil))
> (org-agenda-list-stuck-projects)
> ))
>
> Is it possible to bind it to the standard agenda shortcut C-c a # ? Or
> to achieve the same effect just with special agenda command
> configuration?
Yes it is possible to rebind # in an agenda custom command. I've done
that since I now use non-standard stuck project definitions.
-Bernt
next prev parent reply other threads:[~2010-06-27 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 15:05 Bug: Definition of stuck projects [6.36trans (release_6.36.293.g2e73c)] Jean-Marie Gaillourdet
2010-06-25 20:19 ` Matt Lundin
2010-06-27 7:57 ` Jean-Marie Gaillourdet
2010-06-27 9:41 ` Not a bug, but Jean-Marie Gaillourdet
2010-06-27 12:21 ` Bernt Hansen [this message]
[not found] ` <F4FD2953-6A0D-45F6-8D89-A6B7F357AC30@gaillourdet.net>
[not found] ` <87tyoncsei.fsf@gollum.intra.norang.ca>
2010-06-28 12:18 ` Jean-Marie Gaillourdet
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=87y6e0d5ty.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=jmg@gaillourdet.net \
/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).