From: Carsten Dominik <dominik@science.uva.nl>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Bugs and suggestions for Org 4.70
Date: Wed, 18 Apr 2007 08:55:54 +0200 [thread overview]
Message-ID: <4a1970fd1db8e4018947c9176f0f4164@science.uva.nl> (raw)
In-Reply-To: <871wio1nl8.fsf@bzg.ath.cx>
On Apr 13, 2007, at 14:10, Bastien wrote:
>
>>> - It would be nice if we had some feedback in the modeline telling us
>>> what project / headline is currently clocked in -- suggestion stolen
>>> from the planner mailing list...
>>
>> I like this idea. However, it would probably take up a lot of space
>> in
>> the mode line..... What do you suggest as the content of the label?
>> I
>> guess the elapsed time since the clock was started, and some info
>> about
>> the item.
>
> Yes. Since headlines styles heavily depends on users' habits, why not
> use
> a new format (like `org-email-link-description-format') ?
>
> org-clocked-in-task-modeline-format examples :
>
> "%e - %.15h" : shows elapsed time and the first 15 characters of the
> headline (excluding TODO/tags keywords)
>
> "%e - [%s%d] %t %p %h %T"
> : shows elapsed time, scheduled/dealine state, TODO
> keyword,
> priority, full headline and tags.
>
> "%c (%e)" : only shows parent category elapsed time
>
> Formatting options :
>
> %e elapsed time
> %f file
> %c category
> %t todo state
> %p priority
> %h headline field
> %T tags
> %s scheduled (default: "S" for scheduled)
> %d deadline (default: "D" for deadline)
Since there is always only one project that is being clocked,
this seems a little overkill to me. Maybe a command to jump
to the item being clocked would be more useful.
- Carsten
next prev parent reply other threads:[~2007-04-18 7:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 20:10 Bugs and suggestions for Org 4.70 Bastien
2007-04-13 8:41 ` Carsten Dominik
2007-04-13 10:41 ` Giovanni Ridolfi
2007-04-13 12:10 ` Bastien
2007-04-13 12:38 ` Carsten Dominik
2007-04-13 13:11 ` Bastien
2007-04-18 6:55 ` Carsten Dominik [this message]
2007-04-18 9:17 ` Bastien
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4a1970fd1db8e4018947c9176f0f4164@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=bzg@altern.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.