From mboxrd@z Thu Jan  1 00:00:00 1970
From: Carsten Dominik <dominik@science.uva.nl>
Subject: Re: Re: Bugs and suggestions for Org 4.70
Date: Wed, 18 Apr 2007 08:55:54 +0200
Message-ID: <4a1970fd1db8e4018947c9176f0f4164@science.uva.nl>
References: <87k5willk1.fsf@bzg.ath.cx>
	<dc6c00c39bc3ab4415ad828b5180578b@science.uva.nl>
	<871wio1nl8.fsf@bzg.ath.cx>
Mime-Version: 1.0 (Apple Message framework v624)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1He4Xo-0000I9-AF
	for emacs-orgmode@gnu.org; Wed, 18 Apr 2007 03:25:36 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1He4Xm-0000GK-Uh
	for emacs-orgmode@gnu.org; Wed, 18 Apr 2007 03:25:36 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1He4Xm-0000Fz-Mu
	for emacs-orgmode@gnu.org; Wed, 18 Apr 2007 03:25:34 -0400
Received: from korteweg.uva.nl ([146.50.98.70])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <dominik@science.uva.nl>) id 1He4Sx-0000iz-Vp
	for emacs-orgmode@gnu.org; Wed, 18 Apr 2007 03:20:36 -0400
In-Reply-To: <871wio1nl8.fsf@bzg.ath.cx>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org


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