From: Manish <mailtomanish.sharma@gmail.com>
To: news1142@karl-voit.at
Cc: emacs-orgmode@gnu.org
Subject: Re: Default prewarning time for each deadline
Date: Fri, 6 Apr 2012 12:32:22 +0530 [thread overview]
Message-ID: <CAHuUovXFmZ-mShUuejhWHhCfyrzfW++7Nj-z0nrpZ87XoDdOwQ@mail.gmail.com> (raw)
In-Reply-To: <2012-04-05T22-30-25@devnull.Karl-Voit.at>
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
next prev parent reply other threads:[~2012-04-06 7:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 8:42 Default prewarning time for each deadline Karl Voit
2012-04-05 14:34 ` Michael Brand
2012-04-05 14:54 ` Karl Voit
2012-04-05 18:56 ` Manish
2012-04-05 20:31 ` Karl Voit
2012-04-06 7:02 ` Manish [this message]
2012-04-06 9:25 ` Michael Brand
2012-04-06 10:29 ` changing behavioral for org-deadline-warning-days (was: Default prewarning time for each deadline) Karl Voit
2012-04-09 13:52 ` changing behavioral for org-deadline-warning-days Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHuUovXFmZ-mShUuejhWHhCfyrzfW++7Nj-z0nrpZ87XoDdOwQ@mail.gmail.com \
--to=mailtomanish.sharma@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=news1142@karl-voit.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).