* Weekday repeaters, and filtering scheduled tasks.
@ 2008-06-26 14:21 Avdi Grimm
2008-06-27 2:55 ` Manish
0 siblings, 1 reply; 8+ messages in thread
From: Avdi Grimm @ 2008-06-26 14:21 UTC (permalink / raw)
To: org-mode mailing list
I couldn't find a list of repeaters. Is there by any chance a weekday
repeater that will skip Sat-Sun?
Also, how would I set up an agenda view to show:
- All UNSCHEDULED tasks with the NEXT keyword.
- All scheduled tasks with the NEXT keyword which are DUE or OVERDUE
- NO tasks which are scheduled for future dates.
Thanks!
--
Avdi
Home: http://avdi.org
Developer Blog: http://avdi.org/devblog/
Twitter: http://twitter.com/avdi
Journal: http://avdi.livejournal.com
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Weekday repeaters, and filtering scheduled tasks.
2008-06-26 14:21 Weekday repeaters, and filtering scheduled tasks Avdi Grimm
@ 2008-06-27 2:55 ` Manish
2008-06-27 3:00 ` Avdi Grimm
0 siblings, 1 reply; 8+ messages in thread
From: Manish @ 2008-06-27 2:55 UTC (permalink / raw)
To: Avdi Grimm; +Cc: org-mode mailing list
On Thu, Jun 26, 2008 at 7:51 PM, Avdi Grimm wrote:
>
> I couldn't find a list of repeaters. Is there by any chance a weekday
> repeater that will skip Sat-Sun?
>
> Also, how would I set up an agenda view to show:
>
> - All UNSCHEDULED tasks with the NEXT keyword.
Can you please try this:
(setq org-agenda-custom-commands
(quote (("u" "Unscheduled NEXT entries" todo "NEXT"
((org-agenda-skip-function
(quote (org-agenda-skip-entry-if (quote scheduled)))))))))
I made this using customize interface.
> - All scheduled tasks with the NEXT keyword which are DUE or OVERDUE
I am trying to look up functions that will help identify such
items. But I do not know how to determine today's date in org to
pass to such a function, org-check-before-date for example.
> - NO tasks which are scheduled for future dates.
I do not understand this one.
-- Manish
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Weekday repeaters, and filtering scheduled tasks.
2008-06-27 2:55 ` Manish
@ 2008-06-27 3:00 ` Avdi Grimm
2008-06-27 3:28 ` Manish
0 siblings, 1 reply; 8+ messages in thread
From: Avdi Grimm @ 2008-06-27 3:00 UTC (permalink / raw)
To: org-mode mailing list
On Thu, Jun 26, 2008 at 10:55 PM, Manish <mailtomanish.sharma@gmail.com> wrote:
> I do not understand this one.
I'm looking for the combination of *all* of those conditions in one
agenda view. In other words, I want to see all the NEXT items which
are either unscheduled or due today; but I don't want to see any items
which are scheduled in the future.
--
Avdi
Home: http://avdi.org
Developer Blog: http://avdi.org/devblog/
Twitter: http://twitter.com/avdi
Journal: http://avdi.livejournal.com
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Weekday repeaters, and filtering scheduled tasks.
2008-06-27 3:00 ` Avdi Grimm
@ 2008-06-27 3:28 ` Manish
2008-07-01 23:27 ` Carsten Dominik
0 siblings, 1 reply; 8+ messages in thread
From: Manish @ 2008-06-27 3:28 UTC (permalink / raw)
To: org-mode mailing list
On Fri, Jun 27, 2008 at 8:30 AM, Avdi Grimm wrote:
> On Thu, Jun 26, 2008 at 10:55 PM, Manish wrote:
>> I do not understand this one.
>
> I'm looking for the combination of *all* of those conditions
> in one agenda view. In other words, I want to see all the
> NEXT items which are either unscheduled or due today; but I
> don't want to see any items which are scheduled in the
> future.
Carsten,
May I request some more pre-defined conditions when using
org-agenda-skip-* functions e.g. due and not due, optionally
accepting a date+time to compare against (using current date and
time as default)? Hope this makes sense.
-- Manish
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Weekday repeaters, and filtering scheduled tasks.
2008-06-27 3:28 ` Manish
@ 2008-07-01 23:27 ` Carsten Dominik
2008-07-02 17:38 ` Manish
0 siblings, 1 reply; 8+ messages in thread
From: Carsten Dominik @ 2008-07-01 23:27 UTC (permalink / raw)
To: Manish; +Cc: org-mode mailing list
On Jun 26, 2008, at 8:28 PM, Manish wrote:
> On Fri, Jun 27, 2008 at 8:30 AM, Avdi Grimm wrote:
>> On Thu, Jun 26, 2008 at 10:55 PM, Manish wrote:
>>> I do not understand this one.
>>
>> I'm looking for the combination of *all* of those conditions
>> in one agenda view. In other words, I want to see all the
>> NEXT items which are either unscheduled or due today; but I
>> don't want to see any items which are scheduled in the
>> future.
>
> Carsten,
>
> May I request some more pre-defined conditions when using
> org-agenda-skip-* functions e.g. due and not due, optionally
> accepting a date+time to compare against (using current date and
> time as default)? Hope this makes sense.
>
> -- Manish
>
Hi Manish, I have not done so yet for the skipping mechanism. But I
have just implemented time comparisons for property searches. For
example:
+DEADLINE<"<2008-07-01>"
+DEADLINE>="<now>"
+DEADLINE>"<today>"
+SCHEDULED>="<2008-07-01>"+SCHEDULED<="<2008-07-05>"
I guess this should go a long way....
- Carsten
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Weekday repeaters, and filtering scheduled tasks.
2008-07-01 23:27 ` Carsten Dominik
@ 2008-07-02 17:38 ` Manish
2008-07-02 17:47 ` Carsten Dominik
0 siblings, 1 reply; 8+ messages in thread
From: Manish @ 2008-07-02 17:38 UTC (permalink / raw)
To: Carsten Dominik; +Cc: org-mode mailing list
On Wed, Jul 2, 2008 at 4:57 AM, Carsten Dominik wrote:
>
> On Jun 26, 2008, at 8:28 PM, Manish wrote:
>
>> On Fri, Jun 27, 2008 at 8:30 AM, Avdi Grimm wrote:
>>>
>>> On Thu, Jun 26, 2008 at 10:55 PM, Manish wrote:
>>>>
>>>> I do not understand this one.
>>>
>>> I'm looking for the combination of *all* of those conditions
>>> in one agenda view. In other words, I want to see all the
>>> NEXT items which are either unscheduled or due today; but I
>>> don't want to see any items which are scheduled in the
>>> future.
>>
>> Carsten,
>>
>> May I request some more pre-defined conditions when using
>> org-agenda-skip-* functions e.g. due and not due, optionally
>> accepting a date+time to compare against (using current date and
>> time as default)? Hope this makes sense.
>>
>> -- Manish
>>
>
> Hi Manish, I have not done so yet for the skipping mechanism. But I have
> just implemented time comparisons for property searches. For example:
>
> +DEADLINE<"<2008-07-01>"
> +DEADLINE>="<now>"
> +DEADLINE>"<today>"
> +SCHEDULED>="<2008-07-01>"+SCHEDULED<="<2008-07-05>"
>
> I guess this should go a long way....
Thank you very much.
I have a question though:
,----[ from org.texi ]
| +If the comparison value is enclosed in double quotes @emph{and} angular
| +brackets (like @samp{DEADLINE<="<2008-12-24 18:30>"}), both values are
| +assumed to be date/time specifications in the standard Org way@footnote{The
| +only special values that will be recognized are @samp{"<now>"} for now, and
| +@samp{"<today"} today at 0:00 hours, i.e. without a time specification.}, and
| +the comparison will be done accordingly.
`----
So when I say DEADLINE<="<today>" and if the deadline has a
timestamp ( < current time ), then it will not be listed. Is my
understanding correct? I wonder if "<today>" should not be
better pegged at 23:59 of today's date?
-- Manish
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Weekday repeaters, and filtering scheduled tasks.
2008-07-02 17:38 ` Manish
@ 2008-07-02 17:47 ` Carsten Dominik
2008-07-02 18:47 ` Manish
0 siblings, 1 reply; 8+ messages in thread
From: Carsten Dominik @ 2008-07-02 17:47 UTC (permalink / raw)
To: Manish; +Cc: org-mode mailing list
On Jul 2, 2008, at 10:38 AM, Manish wrote:
> On Wed, Jul 2, 2008 at 4:57 AM, Carsten Dominik wrote:
>>
>> On Jun 26, 2008, at 8:28 PM, Manish wrote:
>>
>>> On Fri, Jun 27, 2008 at 8:30 AM, Avdi Grimm wrote:
>>>>
>>>> On Thu, Jun 26, 2008 at 10:55 PM, Manish wrote:
>>>>>
>>>>> I do not understand this one.
>>>>
>>>> I'm looking for the combination of *all* of those conditions
>>>> in one agenda view. In other words, I want to see all the
>>>> NEXT items which are either unscheduled or due today; but I
>>>> don't want to see any items which are scheduled in the
>>>> future.
>>>
>>> Carsten,
>>>
>>> May I request some more pre-defined conditions when using
>>> org-agenda-skip-* functions e.g. due and not due, optionally
>>> accepting a date+time to compare against (using current date and
>>> time as default)? Hope this makes sense.
>>>
>>> -- Manish
>>>
>>
>> Hi Manish, I have not done so yet for the skipping mechanism. But
>> I have
>> just implemented time comparisons for property searches. For
>> example:
>>
>> +DEADLINE<"<2008-07-01>"
>> +DEADLINE>="<now>"
>> +DEADLINE>"<today>"
>> +SCHEDULED>="<2008-07-01>"+SCHEDULED<="<2008-07-05>"
>>
>> I guess this should go a long way....
>
> Thank you very much.
>
> I have a question though:
>
> ,----[ from org.texi ]
> | +If the comparison value is enclosed in double quotes @emph{and}
> angular
> | +brackets (like @samp{DEADLINE<="<2008-12-24 18:30>"}), both
> values are
> | +assumed to be date/time specifications in the standard Org
> way@footnote{The
> | +only special values that will be recognized are @samp{"<now>"}
> for now, and
> | +@samp{"<today"} today at 0:00 hours, i.e. without a time
> specification.}, and
> | +the comparison will be done accordingly.
> `----
>
> So when I say DEADLINE<="<today>" and if the deadline has a
> timestamp ( < current time ), then it will not be listed. Is my
> understanding correct? I wonder if "<today>" should not be
> better pegged at 23:59 of today's date?
which would fail if you did DEADLINE>="<today>"
There is not good solution for this. <today> uses the date without a
time, in order to provide for comparison with deadline dates that are
only a date, not a time. If your deadlines have times associated with
them, better use a date and time explicitly. I could provide
yesterday and tomorrow, maybe....
- Carsten
>
>
> -- Manish
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Weekday repeaters, and filtering scheduled tasks.
2008-07-02 17:47 ` Carsten Dominik
@ 2008-07-02 18:47 ` Manish
0 siblings, 0 replies; 8+ messages in thread
From: Manish @ 2008-07-02 18:47 UTC (permalink / raw)
To: Carsten Dominik; +Cc: org-mode mailing list
On Wed, Jul 2, 2008 at 11:17 PM, Carsten Dominik wrote:
[snip]
> which would fail if you did DEADLINE>="<today>"
>
> There is not good solution for this. <today> uses the date
> without a time, in order to provide for comparison with
> deadline dates that are only a date, not a time. If your
> deadlines have times associated with them, better use a date
> and time explicitly. I could provide yesterday and
> tomorrow, maybe....
I seem to have found a custom view I am happy with. I am
chainging my old approach of scheduling/deadlining every single
task. Now I schedule something only if it needs to be done on
that day and deadline something only if it's a real
deadline/milestone. This leads to a very small (default) agenda
view of only essential items. But I wanted to list the tasks
currently in progress, list of potential tasks that I can pick up
next and remaining the tasks hence the customized agenda below.
This view/method also seems to fit nicely with using org-depend
to ensure that next sibling gets on the NEXT queue when a task is
marked DONE. The old approach of scheduling/deadlining would
have required that org-depend/TRIGGER property /schedule/ the next
sibling task (just switching the state would not bring it into
agenda view.) This also allows me to fiddle with agenda sorting or
buffer/subtree restrictions to approach work-list in various ways
(e.g. http://www.murtworld.com/2005/04/revolving-workflow-strategies.php).
I am not sure how much "<today>" and "<now>" will help in the
view below.. we shall see. For now I am okay with these
views (and a few exaploratory views.)
(setq org-agenda-custom-commands
(quote (
("zu" "NEXT Tasks - No Specified Duration" tags-todo
"Effort={^$}/!NEXT-DONE-CANCELLED" nil)
("zz" "My Personalized Agenda"
((agenda ""
((org-agenda-overriding-header
"Personalized Agenda:")))
(tags-todo
"+SCHEDULED<=\"<now>\"+DEADLINE<=\"<now>\"/!STARTED"
((org-agenda-overriding-header
"Currently in progress:")))
(tags-todo
"+SCHEDULED<=\"<now>\"+DEADLINE<=\"<now>\"/!NEXT"
((org-agenda-overriding-header "Next
in Queue:")
(org-agenda-sorting-strategy (quote
(category-keep effort-up)))))
(tags-todo
"+SCHEDULED<=\"<now>\"+DEADLINE<=\"<now>\"/!TODO"
((org-agenda-overriding-header "To be Queued:")
(org-agenda-sorting-strategy (quote
(category-keep effort-up)))))) nil))))
As always a big thanks for such an amazingly flexible system.
Best,
-- Manish
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2008-07-02 18:47 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-06-26 14:21 Weekday repeaters, and filtering scheduled tasks Avdi Grimm
2008-06-27 2:55 ` Manish
2008-06-27 3:00 ` Avdi Grimm
2008-06-27 3:28 ` Manish
2008-07-01 23:27 ` Carsten Dominik
2008-07-02 17:38 ` Manish
2008-07-02 17:47 ` Carsten Dominik
2008-07-02 18:47 ` Manish
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).