emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Making an agenda that includes scheduled-for-later tasks?
Date: Fri, 25 Jan 2019 17:10:54 -0500	[thread overview]
Message-ID: <87h8dwfkwh.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 87lg381qus.fsf@llwynog.ekleog.org

Leo Gaspard <orgmode@leo.gaspard.io> writes:

> Hello all!
>
> Just trying to bump this question: How does one make an agenda view that
> includes tasks that are already scheduled for later?
>
> (more details in the quoted mail below)
>
> Cheers,
>   Leo
>
> Leo Gaspard <orgmode@leo.gaspard.io> writes:
>
>> Hello all!
>>
>> I am trying to make an agenda view of all tasks that don't have the
>> :Effort: property set, including tasks that are scheduled for later.
>>
>> My init.el files includes the following lines (of interest is the "E"
>> agenda):
>> ```
>> (setq org-agenda-custom-commands
>>       '(("U" "Unscheduled tasks"
>> 	 todo '("TODO" "WAITING")

[General disclaimer: I can never remember what goes where in org-agenda-custom-commands, and it's
 all untested. Tread carefully.]
 
I don't think the "todo" type can do that. You might want to use the "tags" type with a search
- see

        (info "(org) Matching tags and properties")


It should be something like

       tags "TODO=TODO|WAITING"

or maybe

       tags "TODO=\"TODO|WAITING\""

or maybe

       tags "TODO=\"TODO\"|TODO=\"WAITING\""

(or maybe something else :-) ).

>> 	 ((org-agenda-overriding-header "Unscheduled tasks")
>> 	  (org-agenda-skip-function '(org-agenda-skip-entry-if 'scheduled))))
>> 	("E" "Effortless tasks"
>> 	 todo '("TODO" "WAITING")
>> 	 ((org-agenda-overriding-header "Effortless tasks")
>> 	  (org-agenda-skip-function '(org-agenda-skip-entry-if 'regexp ":Effort:" 'todo '("APPT")))))))
>> ```
>>
>> However, for some reason only tasks that are either not scheduled or
>> scheduled for some time in the past show up in this agenda. This makes
>> it useless, as the point is to remember to put in efforts for every
>> task *before* they are scheduled (and thus started)
>>
>> Do you have an idea what I could have missed?

Maybe (org-agenda-span 'month)?

>>
>> Thanking you in advance,
>>   Leo
>>
>> PS: Also, I've noticed setting =todo '("TODO" "WAITING")= is apparently
>> not enough to get it to ignore the APPT-tagged items, so I've added the
>> filter to =org-agenda-skip-entry-if=. If you have an idea what I'm doing
>> wrong…
>
>

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler

  reply	other threads:[~2019-01-25 22:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 12:42 Making an agenda that includes scheduled-for-later tasks? Leo Gaspard
2019-01-25 19:26 ` Leo Gaspard
2019-01-25 22:10   ` Nick Dokos [this message]
2019-01-26  0:51     ` Leo Gaspard
2019-01-25 21:52 ` Stig Brautaset
2019-01-26  0:57   ` Leo Gaspard

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=87h8dwfkwh.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@gmail.com \
    --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).