org-show-effort ideas

org-show-effort ideas

[Adam Spiers]

I wanted an easy way to see an effort estimate when not in column
view, so I wrote this:

(defun org-show-effort ()
  "Shows the effort of the entry at the current point."
  (interactive)
  (let ((effort (org-entry-get (point) org-effort-property)))
    (message (if effort (format "Effort is %s" effort)
               "No effort defined"))))

However it would be nice to have a keystroke that would do this in
agenda view.  Another nice touch would be to change 'e' which
currently allows you to edit the effort from agenda view, so that the
prompt for the new value shows the existing effort estimate if there
is one.

Regards,
Adam

Re: org-show-effort ideas

[Carsten Dominik]

On Nov 2, 2009, at 2:49 PM, Adam Spiers wrote:

> I wanted an easy way to see an effort estimate when not in column
> view, so I wrote this:
>
> (defun org-show-effort ()
> "Shows the effort of the entry at the current point."
> (interactive)
> (let ((effort (org-entry-get (point) org-effort-property)))
>  (message (if effort (format "Effort is %s" effort)
>             "No effort defined"))))
>
> However it would be nice to have a keystroke that would do this in
> agenda view.  Another nice touch would be to change 'e' which
> currently allows you to edit the effort from agenda view, so that the
> prompt for the new value shows the existing effort estimate if there
> is one.


Admit it: you did not try this :-

The prompt of "e" already does to this, and when you reply
with RET, the same value stays.  I guess this might be good enough
for showing the effort as well?  Otherwise:  Propose a key!

- Carsten

Re: org-show-effort ideas

[Adam Spiers]

On Tue, Nov 03, 2009 at 07:47:48AM +0100, Carsten Dominik wrote:
> On Nov 2, 2009, at 2:49 PM, Adam Spiers wrote:
> 
> >I wanted an easy way to see an effort estimate when not in column
> >view, so I wrote this:
> >
> >(defun org-show-effort ()
> >"Shows the effort of the entry at the current point."
> >(interactive)
> >(let ((effort (org-entry-get (point) org-effort-property)))
> > (message (if effort (format "Effort is %s" effort)
> >            "No effort defined"))))
> >
> >However it would be nice to have a keystroke that would do this in
> >agenda view.  Another nice touch would be to change 'e' which
> >currently allows you to edit the effort from agenda view, so that the
> >prompt for the new value shows the existing effort estimate if there
> >is one.
> 
> Admit it: you did not try this :-
> 
> The prompt of "e" already does to this, and when you reply
> with RET, the same value stays.  I guess this might be good enough
> for showing the effort as well?  Otherwise:  Propose a key!

I definitely did try it, and I just did another 'git pull' and tried
again, and I still don't see it, so I guess we're talking about
different things ;-)

To clarify, I'm referring to showing effort via a single keystroke
when on a todo line in the *Org Agenda* buffer.  Currently, when I hit
"e" on a todo which has an existing "Effort" property value set, my
minibuffer prompt shows "Value: ".  The same applies with C-c C-x e in
a normal .org file buffer.

The only free single keystroke I could find is ' which actually has a
reasonable mnemonic: imagine a contractor providing you with a quote
estimating the effort for a task.

Re: org-show-effort ideas

[Benjamin Andresen]

Hey org-mode,

Adam Spiers <orgmode@adamspiers.org> writes:

> I definitely did try it, and I just did another 'git pull' and tried
> again, and I still don't see it, so I guess we're talking about
> different things ;-)
>
> To clarify, I'm referring to showing effort via a single keystroke
> when on a todo line in the *Org Agenda* buffer.  Currently, when I hit
> "e" on a todo which has an existing "Effort" property value set, my
> minibuffer prompt shows "Value: ".  The same applies with C-c C-x e in
> a normal .org file buffer.

When I press 'e' in an agenda on an item that has the Effort property
value set, I get a minibuffer prompt that shows "Value [5]: " when the
Effort value is 5.

This is with a git version from Sunday morning.

Check the source of the function org-set-effort, it will show you that
it concats "[" cur "]", where cur is the current Effort prop value.

br,
benny

Re: Re: org-show-effort ideas

[Adam Spiers]

Benjamin Andresen (benny@in-ulm.de) wrote:
> Adam Spiers <orgmode@adamspiers.org> writes:
> 
> > I definitely did try it, and I just did another 'git pull' and tried
> > again, and I still don't see it, so I guess we're talking about
> > different things ;-)
> >
> > To clarify, I'm referring to showing effort via a single keystroke
> > when on a todo line in the *Org Agenda* buffer.  Currently, when I hit
> > "e" on a todo which has an existing "Effort" property value set, my
> > minibuffer prompt shows "Value: ".  The same applies with C-c C-x e in
> > a normal .org file buffer.
> 
> When I press 'e' in an agenda on an item that has the Effort property
> value set, I get a minibuffer prompt that shows "Value [5]: " when the
> Effort value is 5.
> 
> This is with a git version from Sunday morning.
> 
> Check the source of the function org-set-effort, it will show you that
> it concats "[" cur "]", where cur is the current Effort prop value.

Thanks for the pointer - it seems that the "[" cur "]" is only
included when

  (org-property-get-allowed-values nil prop 'table)

is nil - and in my case I have a global Effort_ALL property set which
means that this is never the case.  So I think this is a bug which can
be trivially fixed by assigning the prompt string in the let* variable
list, and then using it in both invocations of org-completing-read.

Re: Re: org-show-effort ideas

[Carsten Dominik]

Hi Adam,

On Nov 4, 2009, at 1:26 AM, Adam Spiers wrote:

> Benjamin Andresen (benny@in-ulm.de) wrote:
>> Adam Spiers <orgmode@adamspiers.org> writes:
>>
>>> I definitely did try it, and I just did another 'git pull' and tried
>>> again, and I still don't see it, so I guess we're talking about
>>> different things ;-)
>>>
>>> To clarify, I'm referring to showing effort via a single keystroke
>>> when on a todo line in the *Org Agenda* buffer.  Currently, when I  
>>> hit
>>> "e" on a todo which has an existing "Effort" property value set, my
>>> minibuffer prompt shows "Value: ".  The same applies with C-c C-x  
>>> e in
>>> a normal .org file buffer.
>>
>> When I press 'e' in an agenda on an item that has the Effort property
>> value set, I get a minibuffer prompt that shows "Value [5]: " when  
>> the
>> Effort value is 5.
>>
>> This is with a git version from Sunday morning.
>>
>> Check the source of the function org-set-effort, it will show you  
>> that
>> it concats "[" cur "]", where cur is the current Effort prop value.
>
> Thanks for the pointer - it seems that the "[" cur "]" is only
> included when
>
>  (org-property-get-allowed-values nil prop 'table)
>
> is nil - and in my case I have a global Effort_ALL property set which
> means that this is never the case.  So I think this is a bug which can
> be trivially fixed by assigning the prompt string in the let* variable
> list, and then using it in both invocations of org-completing-read.

You are right, and it is fixed now.

- Carsten