emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kiwon Um <um.kiwon@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-clock mode-line format configuration
Date: Wed, 27 Jan 2010 23:23:18 +0900	[thread overview]
Message-ID: <d24d0f131001270623j10a3fc81o2203344b20177465@mail.gmail.com> (raw)
In-Reply-To: <C71F07BF-556F-4462-9E09-0EB9778FCDBA@gmail.com>

2010/1/27 Carsten Dominik <carsten.dominik@gmail.com>:
>
> On Jan 27, 2010, at 2:33 PM, Kiwon Um wrote:
>
>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>
>>> Hi Um,
>>>
>>> not, the result value has to be a string.
>>>
>>
>> Hi Carsten, hmmm... If you are right, it's an easy problem as long as
>> I'm able to know the variable name containing the string for the mode
>> line at the moment, isn't it?
>
> No, you are misunderstanding.
>
> the variable org-clock-heading-function hast to be set to a function.
> A form starting with `lambda' is a function.
>
> The function needs to return a string, and that string will automatically
> end up
> in the variable `org-clock-heading', which is then used to create the string
> in the mode line.
>
> Clearer now?
>
> I had a typo in the function:
>
> (setq org-clock-heading-function
>     (lambda ()
>        (replace-regexp-in-string
>         "\\[\\[.*?\\]\\[\\(.*?\\)\\]\\]" "\\1"
>         (nth 4 (org-heading-components)))))
>

Cool! Now it's clear.
Really thanks for your kind replies. :)

      reply	other threads:[~2010-01-27 14:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26 10:00 org-clock mode-line format configuration Kiwon Um
2010-01-26 13:07 ` Manish
2010-01-26 22:02 ` Carsten Dominik
2010-01-27  9:25   ` Kiwon Um
2010-01-27 12:59     ` Carsten Dominik
2010-01-27 13:12       ` Kiwon Um
2010-01-27 13:22         ` Carsten Dominik
2010-01-27 13:33           ` Kiwon Um
2010-01-27 13:39             ` Carsten Dominik
2010-01-27 14:23               ` Kiwon Um [this message]

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=d24d0f131001270623j10a3fc81o2203344b20177465@mail.gmail.com \
    --to=um.kiwon@gmail.com \
    --cc=carsten.dominik@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).