Default prewarning time for each deadline

Default prewarning time for each deadline

[Karl Voit]

Hi!

Is there a way to define a default pre-warning time string for new
DEADLINE (only) timestamps?

99% of my DEADLINE timestamps ends with «-0d» as manual pre-warning
time. From time to time I *do* want to use another pre-warning time
such as -10d or -3d. So general deactivation of pre-warnings is not
a solution to me.

I am thinking of using C-c C-d, selecting the day and then something
like DEADLINE: <2012-04-13 Fri -0d> appears. Then I can choose to
keep the default setting or change it to something else like -2d.

Thanks!

-- 
Karl Voit

Re: Default prewarning time for each deadline

[Michael Brand]

Hi Karl

On Thu, Apr 5, 2012 at 10:42, Karl Voit <devnull@karl-voit.at> wrote:
> Is there a way to define a default pre-warning time string for new
> DEADLINE (only) timestamps?

Not in the way you told that you think of. But another solution is to
set org-deadline-warning-days to 0 and then set the
deadline-individual explicit warning period only when not 0. Be aware
of that the behaviour of the deadlines written before and without an
explicit warning period will change. They will not warn any more
before the due date. Adapt them to the new setting where they need
-14d or the like.

Side note: If -3d is typed into the date+time prompt of C-c C-d it
will not end up in the edited Org buffer, so I add it always only
after that step.

Michael

Re: Default prewarning time for each deadline

[Karl Voit]

Hi!

* Michael Brand <michael.ch.brand@gmail.com> wrote:
>
> But another solution is to set org-deadline-warning-days to 0 and
> then set the deadline-individual explicit warning period only when
> not 0.

I tried that but unfortunately with this setting, an entry like
«DEADLINE: <2012-04-23 Mon -20d>» does not appear on todays agenda
at all :-(

Is this due to another setting on my side (only)?

-- 
Karl Voit

Re: Default prewarning time for each deadline

[Manish]

On Thu, Apr 5, 2012 at 2:12 PM, Karl Voit wrote:
> Hi!
>
> Is there a way to define a default pre-warning time string for new
> DEADLINE (only) timestamps?

Have you considered setting org-deadline-warning-days?  It sets the
default warning period for DEADLINE items.

HTH
-- 
Manish

Re: Default prewarning time for each deadline

[Karl Voit]

* Manish <mailtomanish.sharma@gmail.com> wrote:
> On Thu, Apr 5, 2012 at 2:12 PM, Karl Voit wrote:
>> Hi!
>>
>> Is there a way to define a default pre-warning time string for new
>> DEADLINE (only) timestamps?
>
> Have you considered setting org-deadline-warning-days?  It sets the
> default warning period for DEADLINE items.

When I set org-deadline-warning-days to 0, I do not get warnings
even for DEADLINE strings containing a desired warning definition
like -3d :-(

-- 
Karl Voit

Re: Default prewarning time for each deadline

[Manish]

On Fri, Apr 6, 2012 at 2:01 AM, Karl Voit wrote:
> * Manish  wrote:
>> On Thu, Apr 5, 2012 at 2:12 PM, Karl Voit wrote:
>>> Hi!
>>>
>>> Is there a way to define a default pre-warning time string for new
>>> DEADLINE (only) timestamps?
>>
>> Have you considered setting org-deadline-warning-days?  It sets the
>> default warning period for DEADLINE items.
>
> When I set org-deadline-warning-days to 0, I do not get warnings even
> for DEADLINE strings containing a desired warning definition like -3d
> :-(
>

My bad.  I should have read the docstring again before posting.  It
clearly states:

"When 0 or negative, it means use this number (the absolute value of
it) even if a deadline has a different individual lead time
specified."

> I tried that but unfortunately with this setting, an entry like
> «DEADLINE: <2012-04-23 Mon -20d>» does not appear on todays agenda at
> all :-(
>
> Is this due to another setting on my side (only)?

I don't think there's any other setting that helps with this.

-- 
Manish

Re: Default prewarning time for each deadline

[Michael Brand]

Hi all

myself on Thu, Apr 5, 2012 at 16:34:
> But another solution is to
> set org-deadline-warning-days to 0 and then

Karl on Thu, Apr 5, 2012 at 22:31:
> When I set org-deadline-warning-days to 0, I do not get warnings
> even for DEADLINE strings containing a desired warning definition
> like -3d :-(

Manish on Fri, Apr 6, 2012 at 09:02:
> My bad.  I should have read the docstring again before posting.  It
> clearly states:
>
> "When 0 or negative, it means use this number (the absolute value of
> it) even if a deadline has a different individual lead time
> specified."

Since at least Manish and me were surprised by 0 my suggestion is to
use the yet unused nil for what 0 does now (never warn, even if
deadline has an individual lead time) and 0 for what we expected (use
0 if deadline has no individual lead time). The change would break the
customizations that already use 0. In the Org customization survey 0
was not used.
http://orgmode.org/worg/org-configs/org-customization-survey.html

I know, I know, I should read the manual but in this case already the
exemplary variable name itself that documents even the unit of the
value gives me expectations for the positive integers and 0.

Michael

changing behavioral for org-deadline-warning-days (was: Default prewarning time for each deadline)

[Karl Voit]

* Michael Brand <michael.ch.brand@gmail.com> wrote:
> Hi all

Hi!

> Karl on Thu, Apr 5, 2012 at 22:31:
>> When I set org-deadline-warning-days to 0, I do not get warnings
>> even for DEADLINE strings containing a desired warning definition
>> like -3d :-(
>
> Manish on Fri, Apr 6, 2012 at 09:02:
>> My bad.  I should have read the docstring again before posting.  It
>> clearly states:
>>
>> "When 0 or negative, it means use this number (the absolute value of
>> it) even if a deadline has a different individual lead time
>> specified."
>
> Since at least Manish and me were surprised by 0 my suggestion is to
> use the yet unused nil for what 0 does now (never warn, even if
> deadline has an individual lead time) and 0 for what we expected (use
> 0 if deadline has no individual lead time). The change would break the
> customizations that already use 0. 

I see.

Is there a policy regarding to changing behavioral of settings in
Org-mode?

In my personal opinion, changing the code to differ between «nil»
and «0» is not that bad. People might enjoy the additional
feature[1] which does not seem to be implemented so far.

> In the Org customization survey 0 was not used.
> http://orgmode.org/worg/org-configs/org-customization-survey.html

Is there going to be another one? In 2009, I did not even use Emacs
and I'd happy to share my settings as well :-)


<just brainstorming>
Wouldn't it be nice to have a tool that scans for my settings,
compares it for changes/mentions in the changelogs and notifies me
upon matches? :-)
</just brainstorming>


[1] Allowing no warning for each timestamp without explizit warning
period *and/or* allowing warning for explizit warning periods within
timestamps.

-- 
Karl Voit

Re: changing behavioral for org-deadline-warning-days

[Bastien]

Hi Karl,

Karl Voit <devnull@Karl-Voit.at> writes:

> <just brainstorming>
> Wouldn't it be nice to have a tool that scans for my settings,
> compares it for changes/mentions in the changelogs and notifies me
> upon matches? :-)
> </just brainstorming>

actuall there is the :package-version option for defcustom, 
we should use it.  It lets you know when a defcustom has been
introduced and/or changed, so that you get a warning if your
config must be updated.

I'll work on this.

-- 
 Bastien