emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Org-agenda-leaders
Date: Fri, 23 Oct 2015 17:18:30 -0400	[thread overview]
Message-ID: <871tcl8es9.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 87k2qdz5ky.fsf@nicolasgoaziou.fr

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Nick Dokos <ndokos@gmail.com> writes:
>
>> ,----
>> | (defconst org-clock-string "CLOCK:"
>> |   "String used as prefix for timestamps clocking work hours on an item.")
>> | 
>> | (defvar org-closed-string "CLOSED:"
>> |   "String used as the prefix for timestamps logging closing a TODO entry.")
>> | 
>> | (defvar org-deadline-string "DEADLINE:"
>> |   "String to mark deadline entries.
>> | A deadline is this string, followed by a time stamp.  Should be a word,
>> | terminated by a colon.  You can insert a schedule keyword and
>> | a timestamp with \\[org-deadline].")
>> | 
>> | (defvar org-scheduled-string "SCHEDULED:"
>> |   "String to mark scheduled TODO entries.
>> | A schedule is this string, followed by a time stamp.  Should be a word,
>> | terminated by a colon.  You can insert a schedule keyword and
>> | a timestamp with \\[org-schedule].")
>> `----
>>
>> Try redefining some or all of these strings.
>
> Please don't. They should be defconst and are kept as defvar for
> historical reasons.
>

Oops - sorry: I didn't realize that. I didn't even notice the CLOCK
defconst. As a matter of curiosity, what's the back story here?

-- 
Nick

  reply	other threads:[~2015-10-23 21:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20 15:02 Org-agenda-leaders Uwe Jochum
2015-10-21 22:03 ` Org-agenda-leaders Matt Lundin
2015-10-22  6:57   ` Org-agenda-leaders Uwe Jochum
2015-10-22 15:06   ` Org-agenda-leaders Uwe Jochum
2015-10-23  3:12     ` Org-agenda-leaders Nick Dokos
2015-10-23 20:35       ` Org-agenda-leaders Nicolas Goaziou
2015-10-23 21:18         ` Nick Dokos [this message]
2015-10-25 17:31           ` Org-agenda-leaders Nicolas Goaziou

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=871tcl8es9.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).