Tasks performed on a certain day

Tasks performed on a certain day

[Leo Gaspard]

Hello world,

I am trying to figure out a way to represent, in org-mode, tasks that
should be performed exactly on one day of the week. For instance, taking
out the garbage.

It is a task, so I want to be able to mark it as done and not see it for
the rest of the day. But at the same time I can't SCHEDULE <> it,
because otherwise if I don't do it the right day then it still bothers
me the day after, at which I can't do it any longer any way.

Does anyone have a trick to handle this kind of “on-this-date task” with
org-mode?

Cheers,
  Leo

Re: Tasks performed on a certain day

[Eric S Fraga]

On Tuesday,  6 Nov 2018 at 22:59, Leo Gaspard wrote:
> It is a task, so I want to be able to mark it as done and not see it for
> the rest of the day. But at the same time I can't SCHEDULE <> it,
> because otherwise if I don't do it the right day then it still bothers
> me the day after, at which I can't do it any longer any way.

what if you add a, for instance, MISSED task indicator, equivalent to DONE so that you can record that you didn't do the task and then move on to the next scheduled time?

untested...
-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.13-894-gf79545

Re: Tasks performed on a certain day

[Leo Gaspard]

Eric S Fraga <esflists@gmail.com> writes:
> On Tuesday,  6 Nov 2018 at 22:59, Leo Gaspard wrote:
>> It is a task, so I want to be able to mark it as done and not see it for
>> the rest of the day. But at the same time I can't SCHEDULE <> it,
>> because otherwise if I don't do it the right day then it still bothers
>> me the day after, at which I can't do it any longer any way.
>
> what if you add a, for instance, MISSED task indicator, equivalent to
> DONE so that you can record that you didn't do the task and then move
> on to the next scheduled time?

I was hoping for something that would automatically mark the task as
missed (well, I don't care about the task being marked as missed
actually, just about it no longer appearing on my agenda), but I guess
if it's not possible then this can do. Thank you :)

Re: Tasks performed on a certain day

[Ken Mankoff]

[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]

What about passive date stamps?

TODO Thing
<Date>

?

  -k.

Please excuse brevity. Sent from tiny pocket computer with non-haptic
feedback keyboard.

On Tue, Nov 6, 2018, 17:19 Leo Gaspard <orgmode@leo.gaspard.io wrote:

> Eric S Fraga <esflists@gmail.com> writes:
> > On Tuesday,  6 Nov 2018 at 22:59, Leo Gaspard wrote:
> >> It is a task, so I want to be able to mark it as done and not see it for
> >> the rest of the day. But at the same time I can't SCHEDULE <> it,
> >> because otherwise if I don't do it the right day then it still bothers
> >> me the day after, at which I can't do it any longer any way.
> >
> > what if you add a, for instance, MISSED task indicator, equivalent to
> > DONE so that you can record that you didn't do the task and then move
> > on to the next scheduled time?
>
> I was hoping for something that would automatically mark the task as
> missed (well, I don't care about the task being marked as missed
> actually, just about it no longer appearing on my agenda), but I guess
> if it's not possible then this can do. Thank you :)
>
>

[-- Attachment #2: Type: text/html, Size: 1741 bytes --]

Re: Tasks performed on a certain day

[Leo Gaspard]

Ken Mankoff <mankoff@gmail.com> writes:

> What about passive date stamps?
>
> TODO Thing
> <Date>
>
> ?

That's exactly what I was looking for! I hadn't seen an example with
TODO coupled with <> dates, and didn't think it'd have a special
behavior.

Thank you and Marcin for this solution!

Cheers,
  Leo

Re: Tasks performed on a certain day

[Marcin Borkowski]

On 2018-11-07, at 12:33, Leo Gaspard <orgmode@leo.gaspard.io> wrote:

> Ken Mankoff <mankoff@gmail.com> writes:
>
>> What about passive date stamps?
>>
>> TODO Thing
>> <Date>
>>
>> ?
>
> That's exactly what I was looking for! I hadn't seen an example with
> TODO coupled with <> dates, and didn't think it'd have a special
> behavior.
>
> Thank you and Marcin for this solution!

Glad to know that they work!

BTW, AFAIR they are called "plain" timestamps.

Best,

-- 
Marcin Borkowski
http://mbork.pl

Re: Tasks performed on a certain day

[Samuel Wales]

i also call them event.

i have code below that shows them in agenda as "Event:" in their own face.

i think there was a proposal a while back to have them be in the
planning line [the one just after the header] as EVENT: <...> along
with closed, scheduled, and deadline.  i kinda liked that proposal
[great for 3rd party tools, maybe even a bit faster, consistency] but
it never went anywhere.  :]

===

note: i am not signed up with fsf.

commit 33a49662f7b89e9fd52742a59542dfb0f116e715 (HEAD, refs/heads/local)
Author: Your Name <you@example.com>
Date:   2015-08-08 13:10:12 -0700

    === alpha add one space to leaders, add Event:, format state better

	Modified   lisp/org-agenda.el
diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index 234c0da..268aa00 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -5593,7 +5593,10 @@ displayed in agenda view."
 		   (habit? (and (fboundp 'org-is-habit-p) (org-is-habit-p)))
 		   (item
 		    (org-agenda-format-item
-		     (and inactive? org-agenda-inactive-leader)
+                     (if inactive?
+                         org-agenda-inactive-leader
+                       ;; alpha this could be an org-agenda-event-leader
+                       "Event:     ")
 		     head level category tags time-stamp org-ts-regexp habit?)))
 	      (org-add-props item props
 		'priority (if habit?
@@ -5609,7 +5612,7 @@ displayed in agenda view."
 		'warntime warntime
                 ;; =alpha this adds inactive timestamp face
                 ;; how i figured this out, i do not know
-                'face (if inactivep
+                'face (if inactive?
                           'org-agenda-inactive
                         'org-agenda-calendar-event)
 		'type "timestamp")
@@ -5814,9 +5817,16 @@ then those holidays will be skipped."
 		(setq txt (concat txt " - " extra))))
 	    (setq txt (org-agenda-format-item
 		       (cond
-			(closedp "Closed:    ")
-			(statep (concat "State:     (" state ")"))
-			(t (concat "Clocked:   (" clocked  ")")))
+                         (closedp "Closed:    ")
+                         ;; alpha the only issue here is somehow
+                         ;; we have to turn off my inactive,
+                         ;; which picks this up redundantly
+                         (statep (format "S(%7.7s) " state))
+                         ;; ;; alpha adding one space because line up
+                         ;; (statep (concat "State:      (" state ")"))
+                         ;; (t (format "C(%7.7s) " clocked)))
+                         ;; alpha adding one space because line up
+                         (t (concat "Clocked:    (" clocked  ")")))
 		       txt level category tags timestr)))
 	  (setq priority 100000)
 	  (org-add-props txt props

[back]

Re: Tasks performed on a certain day

[Nicolas Goaziou]

Hello,

Samuel Wales <samologist@gmail.com> writes:

> i also call them event.
>
> i have code below that shows them in agenda as "Event:" in their own face.
>
> i think there was a proposal a while back to have them be in the
> planning line [the one just after the header] as EVENT: <...> along
> with closed, scheduled, and deadline.  i kinda liked that proposal
> [great for 3rd party tools, maybe even a bit faster, consistency] but
> it never went anywhere.  :]

It is tempting to add a new planning keyword, indeed. Agenda generation
would be much faster (looking for timestamps everywhere is the slowest
part of agenda generation).

However, I think some users need to have multiple so-called events in
the same headline, e.g., for irregularly repeating tasks.

Regards,

-- 
Nicolas Goaziou

Re: Tasks performed on a certain day

[Gregor Zattler]

Hi Nicolas, org mode users and developers,
* Nicolas Goaziou <mail@nicolasgoaziou.fr> [2018-11-08; 18:34]:
> However, I think some users need to have multiple so-called events in
> the same headline, e.g., for irregularly repeating tasks.

Yes, I do this all the time.  For instance there is a heading for
visits at the dentist in my org file which contains plain
timestamps for every day I went there.  This is quite handy as
I'm able to tell when I was there with a glance at this list of
plain stamps.  This may be helpful when dealing with the
insurance company.

If a heading could only hold one event timestamp I would need
much more headings which look somewhat heavy because of the
markup, the way they are shown and most probably would also
feature a drawer each .  OTHT I could then archive all old visits
at the dentist, have a smaller org file but it would be more
difficult to reconstruct past dates with my dentist.  Because
then they would be scattered among other headings in the archive
file and the only way of finding out would be to generate an
agenda from the archive file.


Ciao; Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-

Re: Tasks performed on a certain day

[Marcin Borkowski]

On 2018-11-06, at 14:59, Leo Gaspard <orgmode@leo.gaspard.io> wrote:

> Hello world,
>
> I am trying to figure out a way to represent, in org-mode, tasks that
> should be performed exactly on one day of the week. For instance, taking
> out the garbage.
>
> It is a task, so I want to be able to mark it as done and not see it for
> the rest of the day. But at the same time I can't SCHEDULE <> it,
> because otherwise if I don't do it the right day then it still bothers
> me the day after, at which I can't do it any longer any way.
>
> Does anyone have a trick to handle this kind of “on-this-date task” with
> org-mode?

Why don't you just say this?

* TODO <2018-11-14 śro +1w> Take out the trash

Hth,

--
Marcin Borkowski
http://mbork.pl