I have tasks that I do every day (e.g bugzilla triage), but I only do those Monday to friday. Not on the weekends.
When I use something like this:
SCHEDULED: <2015-02-07 Sat ++1d>
It repeats it every day, including weekends. Can I change this?
If you just need a reminder, and don't need to mark them as 'DONE' in your org-file, you could use the calendar integration for these situations.
** Triage Bugzilla Entries 09:00-10:00
<%%(memq (calendar-day-of-week date) '(1 2 3 4 5))>
This will insert an entry into your daily agenda for weekdays only, but not a task.
Unfortunately, org-mode doesn't seem to support this in a simple command, but you can replicate this by setting up multiple weekly repeats for the same item like so:
* TODO My task
SCHEDULED: <2015-02-09 Mon ++1w>
SCHEDULED: <2015-02-10 Tue ++1w>
SCHEDULED: <2015-02-11 Wed ++1w>
SCHEDULED: <2015-02-12 Thu ++1w>
SCHEDULED: <2015-02-13 Fri ++1w>
One way is to simply have a TODO for each week day, eg:
* TODO My task
SCHEDULED: <2015-02-09 Mon ++1w>
* TODO My task
SCHEDULED: <2015-02-10 Tue ++1w>
This is different than another answer:
* TODO My task
SCHEDULED: <2015-02-09 Mon ++1w>
SCHEDULED: <2015-02-10 Tue ++1w>
SCHEDULED: <2015-02-11 Wed ++1w>
SCHEDULED: <2015-02-12 Thu ++1w>
SCHEDULED: <2015-02-13 Fri ++1w>
Which has an issue, as pointed out by someone:
There is an issue with this. When I close a task, it moves all the scheduled items forward by a week, not just the one that is due :-/
This issue occurs because all timestamps are associated with one TODO.
Related
In org mode, I have a set of tasks with time estimates. I'd like to sum the time estimates only for those tasks not marked DONE, to get an estimate of the remaining time to completion.
To give a toy example, suppose my tasks are:
* A sample project
** DONE Task 1
CLOSED: [2022-03-25 Fri 21:30]
:PROPERTIES:
:EFFORT: 2:00
:END:
:LOGBOOK:
CLOCK: [2022-03-25 Fri 20:30]--[2022-03-25 Fri 21:30] => 1:00
:END:
** TODO Task 2
:PROPERTIES:
:EFFORT: 1:00
:END:
** TODO Task 3
:PROPERTIES:
:EFFORT: 0:30
:END:
My column set up is:
#+COLUMNS: %38ITEM(Details) %TAGS(Context) %7TODO(To Do) %6CLOCKSUM(Clock) %5Effort(Est){:}
When I bring up column view, I get an estimate of 3:30, the sum of all the tasks. But what I'd like is an estimate with only the tasks not marked DONE -- 1:30. Is there a way to achieve that?
Suppose I plan to meet with someone multiple times, but not on a regular schedule that would allow me to set it as a repeating task. I can type in something like
** TODO Meeting with Gus
SCHEDULED: <2014-04-25 FRI 10:00-10:30>
SCHEDULED: <2014-04-28 MON 15:30-16:00>
Scheduling the first meeting using C-c C-s (org-schedule) is easy enough. I cannot find a way to schedule the second without typing everything in by hand. If I hit C-c C-s again, it changes the time of the first meeting rather than scheduling a second meeting. Is there a more efficient way to do this?
How about:
** Meet with a dude
<2014-04-25 Fri 13:00-13:30>
<2014-04-27 Sun 14:00-14:30>
<2014-04-29 Tue 10:00-10:30>
<2014-05-02 Fri 08:00-08:30>
This will show up in your agenda at the indicated times.
I started getting this issue with repeated tasks now. Assume I have a task like this:
** TODO test task
SCHEDULED: <2013-11-12 Tue + 1m>
I want to close and schedule it for next month. So I do C-c C-t. After doing this I get the following:
** DONE test task
CLOSED: [2013-11-12 Tue 17:10] SCHEDULED: <2013-11-12 Tue + 1m>
- CLOSING NOTE [2013-11-12 Tue 17:10]
Issues:
As you can see, the scheduled date is same as the old date.
TODO has changed to DONE. It should stay in TODO with the new scheduled dates.
This issue started appearing recently. Any help is appreciated.
Remove the space between + and 1m.
I am using Emacs org-mode. Assume it is 2012-11-10 (today) and I have a TODO item:
**** LATER [#D] call John :phone:
SCHEDULED: <2012-07-23 Mon .+1m>
- State "DONE" from "TODO" [2012-06-23 Sat 12:21]
:PROPERTIES:
:LAST_REPEAT: [2012-06-23 Sat 12:21]
:END:
In the agenda view that I get with Ctrl-c a a this shows up as:
TODO: Sched.19x: LATER [#D] call John :phone:
and is sorted among the other items that have a SCHEDULED date 19 days ago. However, the item above has not been worked on for almost four months, so it should actually be sorted among the items SCHEDULED on <2012-07-23 Mon> (~110 days ago).
I consider this a bug, but I wanted to know whether there is any option I could try to fix that behavior. I have searched the internet for over an hour but did not find a solution.
It's not a bug but the expected behavior.
You scheduled the task with the repeated interval
SCHEDULED: <2012-07-23 Mon .+1m>
which means that the task is kinda re-scheduled every month. The last time it was 2012-10-27, 19 days ago.
You can remove the repeated interval
SCHEDULED: <2012-07-23 Mon>
then the task will be shown as scheduled 110 days ago.
I want to schedule a task in emacs org-mode to show up multiple times during the day.
Edit: as an example suppose I want yo call my wife every 2 hours during the day.
According to the Org Mode manual on Repeated Tasks there is an hourly repeater:
In the following example
** TODO Pay the rent
DEADLINE: <2005-10-01 Sat +1m>
the +1m is a repeater; the intended interpretation is that the task
has a deadline on <2005-10-01> and repeats itself every (one) month
starting from that time. You can use yearly, monthly, weekly, daily
and hourly repeat cookies by using the y/w/m/d/h letters.
You may use something like that:
* TODO Call Wife
DEADLINE: <2013-02-17 Sun 16:00 +2h>
Unfortunately, I've noticed that special repeater modifiers (++ and .+) do not work properly for hourly repeaters. The manual says:
** TODO Call Father
DEADLINE: <2008-02-10 Sun ++1w>
Marking this DONE will shift the date by at least one week,
but also by as many weeks as it takes to get this date into
the future. However, it stays on a Sunday, even if you called
and marked it done on Saturday.
Based on this, you would expect that marking an entry with an hourly repeater (such as the one above) DONE would "shift time by at least n hours but also as many hours as it takes to get this date into the future".
However, here's what I got after marking both entries DONE:
** TODO Call Father
DEADLINE: <2013-03-03 Sun ++1w>
- State "DONE" from "TODO" [2013-02-25 Mon 23:06]
:PROPERTIES:
:LAST_REPEAT: [2013-02-25 Mon 23:06]
:END:
** TODO Call Wife
DEADLINE: <2013-02-17 Sun 18:00 ++2h>
- State "DONE" from "TODO" [2013-02-25 Mon 23:06]
:PROPERTIES:
:LAST_REPEAT: [2013-02-25 Mon 23:06]
:END:
As you can see, the time in the second entry has shifted to 18:00, but the date is still the same.
Concerning an approach for creating repeating items explicitly another feature could be useful. The manual says:
An alternative to using a repeater is to create a number of copies of
a task subtree, with dates shifted in each copy. The command C-c C-x c
was created for this purpose, it is described in Structure editing.
But unfortunately, it doesn't work with hours.
Information in this post based on Org Mode version 7.9.3.e.
In the absence of hour/minute level repeaters, if the interval is not too small, you might add multiple timestamps for the hours, while using the other facilities for repeated items:
** Testentry
<2012-01-19 Do 10:00 +1w>
<2012-01-19 Do 12:00 +1w>
The resulting agenda view
Thursday 19 January 2012
Calendar: 10:00...... Testentry
Calendar: 12:00...... Testentry
[...]
Thursday 26 January 2012
8:00...... ----------------
Calendar: 9:45-10:00 XXXXXXXXXXXXXX :OFFICE:
10:00......
Calendar: 10:00...... Testentry
10:00...... ----------------
Calendar: 12:00...... Testentry
[...]