From: Samuel Wales <email@example.com>
Subject: deadline warning days entry
Date: Wed, 22 Jul 2020 23:21:23 -0700 [thread overview]
Message-ID: <CAJcAo8si_mY187rAfOvU2zdRkcip2b9MdGexud-bisYD4fK5+Q@mail.gmail.com> (raw)
i tend to want either zero or some number [like 4 or 8] for deadline
warning days for deadline timestamps [tses].
so i set the deadline warning days variable to a nonzero positive
number as a default. and then manually add -0d to individual tses
when i want -0d.
however, manual editing feels quite error prone and it is
typing/concentration-intensive. the failure mode could include not
being warned or even not showing the deadline at all.
the existing command has a prefix option, but it does not solve the problem.
c-u c-u will ask you for a warning date, but for less chance of error,
i want an interval or number of dasys instead. this would also be
slightly more consistent with the variable, which takes an integer. a
warning date requires you to think about date arithmetic.
another problem with c-u -cu is that it requires you to enter the ts,
then do c-u c-u. i.e. you can't enter a deadline with c-u c-u.
if those two problems were fixed, i would have no issue.
i'd like to know if anybody has any code for changing the deadline
warning days of a deadline ts to an interval or ndays. [the minus
sign would not be needed.] this would be for new tses and existing
tses. in my case it would default to my alternate interval [0d].
this could be thought of as a feature request, but i don't know if it
is of enough interest, and i figured perhaps somebody already has some
code for this or likes the idea above also.
The Kafka Pandemic
What is misopathy?
reply other threads:[~2020-07-23 6:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).