From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: org-agenda-ignore-scheduled not taken into account in custom agenda blocks?
Date: Fri, 16 Nov 2012 09:40:16 +0800 [thread overview]
Message-ID: <871ufu8gvz.fsf@ericabrahamsen.net> (raw)
In-Reply-To: m2haoqdeap.fsf@polytechnique.org
Alan Schmitt <alan.schmitt@polytechnique.org> writes:
> Hello,
>
> I'm implementing some of the ideas of the great norang page
> (http://doc.norang.ca/org-mode.html), but there is one thing that is
> failing me. I can see that "org-agenda-ignore-scheduled" work for the
> global todo list, but it does not seem to be working when using a custom
> block. For instance, using the following definition:
>
> #+BEGIN_SRC elisp
> (tags-todo "-WAITING-CANCELLED/!NEXT"
> ((org-agenda-overriding-header "Next Tasks")
> (org-agenda-skip-function 'bh/skip-projects-and-habits-and-single-tasks)
> (org-agenda-todo-ignore-scheduled t)
> (org-agenda-todo-ignore-deadlines t)
> (org-agenda-todo-ignore-with-date t)
> (org-tags-match-list-sublevels t)
> (org-agenda-sorting-strategy
> '(todo-state-down effort-up category-keep))))
> #+END_SRC
>
> I still see scheduled tasks.
>
> Is it supposed to be working or am I doing it wrong?
I can confirm that scheduled and deadlined TODOs still show up where
they shouldn't -- I tried putting the ignore statements both in the
individual block declarations, and in the declaration at the end of the
custom command. This is with org-version "7.9.2".
Seems like a bug!
Eric
next prev parent reply other threads:[~2012-11-16 1:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 16:25 org-agenda-ignore-scheduled not taken into account in custom agenda blocks? Alan Schmitt
2012-11-16 1:40 ` Eric Abrahamsen [this message]
2012-11-20 15:36 ` Alan Schmitt
2012-11-20 16:12 ` Samuel Wales
2012-11-20 19:28 ` Alan Schmitt
2012-11-20 20:21 ` Samuel Wales
2012-11-21 7:30 ` Alan Schmitt
2012-11-24 16:11 ` Bernt Hansen
2012-11-24 16:07 ` Bernt Hansen
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=871ufu8gvz.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).