From: Carsten Dominik <email@example.com>
To: Bernt Hansen <firstname.lastname@example.org>
Subject: Re: GOAL keyword with DEADLINE semantics?
Date: Tue, 10 Mar 2009 18:52:17 +0100 [thread overview]
Message-ID: <9E9150AF-7AE6-4631-888C-3707B7884DFA@uva.nl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1437 bytes --]
On Mar 9, 2009, at 3:35 PM, Bernt Hansen wrote:
> Carsten Dominik <email@example.com> writes:
>> (setq org-deadline-string "DUE:")
>> which captures both the colors of DEADLINE and GOAL pretty well, I
>> In fact, I wish I had made this the default from beginning,
>> a much shorter and nicer word. Now it is too late to change this, I
>> am afraid.....
> Is it really too late? Could you maybe make the REGEXP that matches
> deadline look for both DEADLINE: and DUE: but make new deadlines use
> DUE: ?
> As long as you don't force everyone to s/DEADLINE:/DUE:/ in their
> existing setup I don't think there's a huge impact with this change.
I guess I meant it is too late to *only* change that variable.
You are right, in principle this could be done. Which basically means
implementing Austin's proposal of allowing several deadline keywords.
But: it means changing quite a few regexps, not just one. And it
will mean follow-up requests to have different fontification
for different DEADLINE keywords. And different appearance
in the Agenda. And adding the deadline keyword to the CSV export
of the agenda. And doing everything the same for variations
on SCHEDULED. And something I have not thought of yet... :-)
When I am in a good mood, maybe...
P.S. Talking about mood: Ever seen a man in a bad mood?
[-- Attachment #1.2: Type: text/html, Size: 2384 bytes --]
[-- Attachment #2: Type: text/plain, Size: 204 bytes --]
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
next prev parent reply other threads:[~2009-03-10 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-08 15:36 GOAL keyword with DEADLINE semantics? Austin Frank
2009-03-08 22:54 ` Shelagh Manton
2009-03-09 12:01 ` Carsten Dominik
2009-03-09 14:35 ` Bernt Hansen
2009-03-10 17:52 ` Carsten Dominik [this message]
2009-03-10 7:15 ` Austin Frank
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).