Samuel Loury writes:
> May be I should also consider sending you a cheesecake ;-)
Well, cheesecake don't travel very well through the Atlantic,
a postcard would do! :)
--
Bastien
Bastien writes:
> Point well taken -- this is now what adding "--2d" does: use a
> temporary delay that will not be taken into account for dates later
> than the next repeater, and that will be deleted when a repeating
> task is marked as done. Thanks for suggesting this.
Thanks for the --2d fe
I just got this installed today and it appears to be *exactly* what I
wanted.
Many thanks for this implementation. Your cheesecake is in the mail. :)
:AMN:
On 02/07/2013 01:44 AM, Bastien wrote:
Hi Andrew,
"Andrew M. Nuxoll" writes:
If you do that, I may have to send you a cheesecake.
T
Hi Bastien
On Tue, Feb 12, 2013 at 5:33 PM, Bastien wrote:
> This should be fixed now. Thanks for the clear example and the
> testing.
Thank you for fixing the bugs and mainly for the --2d delay for
repeated SCHEDULED.
To summarize my point of view of this thread: Originally I wanted to
use su
Hi Michael,
Michael Brand writes:
> This
>
> * TODO 1a
> SCHEDULED: <2013-01-10 Thu +1m --2d>
> * TODO 2a
> SCHEDULED: <2013-02-10 Sun +1m --2d>
> * TODO 1b
> SCHEDULED: <2013-01-11 Fri +1m --2d>
> * TODO 2b
> SCHEDULED: <2013-02-11 Mon +1m --2d>
> * TODO 1c
> SCHEDULED: <2013-01-12 Sa
Hi Michael,
Michael Brand writes:
> And there is a critical bug: Setting 2a to DONE repeats all entries
> below too.
I fixed this one. I'm looking in the other issue right now.
Thanks!
--
Bastien
On Tue, Feb 12, 2013 at 1:29 PM, Michael Brand
wrote:
> And there is a critical bug: Setting 2a to DONE repeats all entries
> below too.
Reducing to a MCE shows me that triggering the repetitions requires
#+STARTUP: nologrepeat
Michael
Hi Bastien
On Tue, Feb 12, 2013 at 11:21 AM, Bastien wrote:
> Point well taken -- this is now what adding "--2d" does: use a
> temporary delay that will not be taken into account for dates later
> than the next repeater, and that will be deleted when a repeating
> task is marked as done. Thanks
Hi Michael,
Michael Brand writes:
>> SCHEDULED: <2013-02-07 jeu. -2d>
>>
>> The item will not be shown today, but in three days.
>
> For this case I would use:
>
> SCHEDULED: <2013-02-09 Sat>
AFAIU this would not work for what Andrew wants. He wants the
scheduled item to be invisible on th
Hi Samuel
On Sat, Feb 9, 2013 at 7:06 PM, Samuel Loury wrote:
> [...]
> I quite agree with you. It is also the way I understood it, with the
> automatic removal of the -3d.
>
> Only a tiny glitch there, I suppose you guessed it was written
>
> SCHEDULED: <2013-02-01 Fri +1m -3d>
>
> and not
>
> S
Hi,
Michael Brand writes:
> The usefulness of a SCHEDULED delay I see together with a TODO and
> repeater to implement an _exception_ (to simplify: exception just for
> the first date, before the repetitions). For example
>
> SCHEDULED: <2013-02-01 Fri +1w -3d>
>
> would mean: Usually start wor
Hi Bastien
On Thu, Feb 7, 2013 at 10:44 AM, Bastien wrote:
> You can now use a "delay cookie" like this:
>
> SCHEDULED: <2013-02-07 jeu. -2d>
>
> The item will not be shown today, but in three days.
For this case I would use:
SCHEDULED: <2013-02-09 Sat>
It seems I don’t get the point becau
On Fri, Jan 25, 2013 at 12:10 PM, Michael Brand
wrote:
> Let me only suggest an idea to deal with this, item-based: When the
> DEADLINE “warning period” would be generalized to allow positive
> numbers then it would extend to a “warning and delay period”. Starting
> with:
>
> * TODO [#B] Verify lo
Hi Andrew,
"Andrew M. Nuxoll" writes:
> If you do that, I may have to send you a cheesecake.
Time for a cheesecake!
You can now use a "delay cookie" like this:
SCHEDULED: <2013-02-07 jeu. -2d>
The item will not be shown today, but in three days.
See the new options `org-scheduled-delay-da
Hi Andrew !
Sorry, but I forgot to include one line:
(setq org-date-state-wait-state "PENDING")
to define the state, that the node should be changed to
(I have "PENDING" among my org-states).
Now if I have a node like this:
* TODO Foo
and invoke org-date-state, I get asked for a date (lets
If you do that, I may have to send you a cheesecake.
Thank you!
:AMN:
On 01/25/2013 02:45 AM, Bastien wrote:
Hi Andrew,
thanks for explaining it so clearly, I understand the need,
and I also understand my suggestion (and Eric's one, FWIW)
cannot completely satisfy it.
I will provide a patch f
That looks like a delay period on a SCHEDULED item would work very well
for me. I can see the positive delay period being useful to me as well.
This does look like it would be more difficult to implement because it's
a subtle change to existing code rather than something more modular.
:AMN:
Hi Andrew,
thanks for explaining it so clearly, I understand the need,
and I also understand my suggestion (and Eric's one, FWIW)
cannot completely satisfy it.
I will provide a patch for this next week, we can discuss it
afterwards.
All best,
--
Bastien
Hi Andrew
On Thu, Jan 24, 2013 at 11:54 PM, Andrew M. Nuxoll wrote:
> Here an example scenario that illustrates my problem: Say, at the end of
> each week I need to sit down and generate a report on my progress to send to
> the boss. So I have recurring, weekly TODO entry on Friday morning. We
"Andrew M. Nuxoll" writes:
[...]
> Furthermore, a delayed TODO item should have more urgency since it's
> been delayed. But creating a copy means i can't do that. When Monday
> rolls around and it's time to prepare that report it shows up in green
> text like this in my agenda:
> S
Bastien:
Thanks for your patience and continued assistance.
Here an example scenario that illustrates my problem: Say, at the end
of each week I need to sit down and generate a report on my progress to
send to the boss. So I have recurring, weekly TODO entry on Friday
morning. Well, one we
Hi Andrew,
"Andrew M. Nuxoll" writes:
> My first problem is that C-h is mapped to backspace on my computer.
> I presume (C-h v) means view help on a particular item.
C-h v is normally bound to `describe-variable'.
So you can run this:
M-x describe-variable RET org-agenda-todo-ignore-timestam
Hi Andrew,
some time ago I did somethin similar (see below), it works with properties and
might
come close, to what you want ...
best regards, Marc
(defun org-date-state (arg)
"Save away state for current node; with prefix restore for all nodes if time has
passed."
(interactive "P")
(i
Bastien:
I sense that your reply contains the key to the functionality that I
want but I find I am unable to figure it out. I'm sorry to bother you
further but I would be grateful for a little more direction.
My first problem is that C-h is mapped to backspace on my computer. I
presume (C-
Hi Andrew
On Wed, Jan 23, 2013 at 7:51 PM, Andrew M. Nuxoll wrote:
> * TODO [#B] Verify login to the virtual machines
> SCHEDULED: <2013-01-24 Thu>
> SCHEDULED: <2013-01-29 Tue +1w>
>
> and I mark the item as done via agenda mode (by hitting 't') it changes to
> this:
>
> * TODO [#B] Verify l
Sam:
I'd be delighted if you did this. I suspect you could do it in 1/10th
the time that it would take me to figure it out.
In the example below, I would want the "Verify login..." entry to
reappear on the agenda starting on 2013-01-24 Thu. The easiest way to
do this might be to just autom
Michael:
Thank you for this info. I didn't know that you could add two scheduled
dates to a task! Unfortunately, org-mode doesn't handle the dual
schedule the way I would wish. For example if I have:
* TODO [#B] Verify login to the virtual machines
SCHEDULED: <2013-01-24 Thu>
SCHEDULED:
Hi Andrew
On Mon, Jan 21, 2013 at 7:20 PM, Andrew M. Nuxoll wrote:
> I'd like to modify the org-mode code to support the following:
>
> 1. Add a date tag to an entry that indicates that it is "inactive" until a
> certain date. I'm picturing something like this:
>
> * TODO [#B] Verify login
Hi Andrew,
"Andrew M. Nuxoll" writes:
> 1. Add a date tag to an entry that indicates that it is "inactive" until a
> certain date. I'm picturing something like this:
>
> * TODO [#B] Verify login to the virtual machines
> SCHEDULED: <2013-01-11 Tue +1w> DELAY: <2013-01-24 Thu>
>
> 2.
"Andrew M. Nuxoll" writes:
> 1. Add a date tag to an entry that indicates that it is "inactive"
> until a certain date. I'm picturing something like this:
>
> * TODO [#B] Verify login to the virtual machines
>SCHEDULED: <2013-01-11 Tue +1w> DELAY: <2013-01-24 Thu>
>
In your model,
A while ago I posted for help in adding an ability to "snooze" a to-do item:
http://www.mail-archive.com/emacs-orgmode@gnu.org/msg20114.html
At the time, the only solution available was to create a manual copy of
the item. This approach creates as many problems as it solves for me.
I've gott
31 matches
Mail list logo
