From: Carsten Dominik <carsten.dominik@gmail.com>
To: Kiwon Um <um.kiwon@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-clock mode-line format configuration
Date: Wed, 27 Jan 2010 13:59:35 +0100 [thread overview]
Message-ID: <48AC00D2-F7E0-47AE-8384-B4A59C63C9CE@gmail.com> (raw)
In-Reply-To: <m3r5pbew7d.fsf@gmail.com>
On Jan 27, 2010, at 10:25 AM, Kiwon Um wrote:
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> On Jan 26, 2010, at 11:00 AM, Kiwon Um wrote:
>>
>>> Dear orgmode dev team:
>>>
>>> When the clock is started on an item, the item is shown on the mode
>>> line. But the string on the mode line just shows the raw string of
>>> the
>>> item, so sometimes it looks ugly when it contains a link.
>>>
>>> So I suggest to make it customizable,
>>
>> It is customizable, see the variable org-clock-heading-function
>>
>
> Would you please show me the function defun doing what I want? I have
> no idea to how to build org-clock-heading.
Untested:
(setq org-clock-heading-function
(lambda ()
(replace-regexp-in-string
"\\[\\[.*?\\]\\[\\(.*?\\)\\]\\]" "\\1"
(nth 4 org-heading-components))))
>
>>> or to vanish the link string, e.g.
>>> using
>>> (replace-regexp-in-string "\\[\\[.*\\]\\[\\(.*\\)\\]\\]" "\\1" str)
>>
>> Yes, that makes sense, I have added this. I have changed the "*"
>> parts
>> to non-greedy though, in case there are several links in the line.
>>
>
> Cool. I missed that.
> (replace-regexp-in-string "\\[\\[.*?\\]\\[\\(.*?\\)\\]\\]" "\\1" s))
>
> Kiwon Um
- Carsten
next prev parent reply other threads:[~2010-01-27 12:59 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 [this message]
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
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=48AC00D2-F7E0-47AE-8384-B4A59C63C9CE@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=um.kiwon@gmail.com \
/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).