Re: [Orgmode] bug? - can't set effort from agenda

[George Pearson]

On 25 Oct 2010 at 17:45, Carsten Dominik wrote:

> 
> 
> However, what we still need is this:
> 
> Make your file as small as possible so that it still repeats the bug.
> 
><snip>
> 
> Then: how do you construct the agenda view?  Is it the daily agenda,  
> or a TODO list.  What does it look like?  In which line is the cursor  
> when you press "e"?  Is that line linking to the first task in your  
> org file, or the last?

OK, here is master.org and recurring.org.:

--------------------  master.org -----------------------------------
#+STARTUP: odd
#+STARTUP: hidestars
#+STARTUP: logdone
#+SEQ_TODO: TODO NEXT PENDING | DONE(d!) CANCELLED(c@)
#+TAGS: Rock(r) Frog(f) Schedule(s) Important(i) Urgent(u) Week(w) Soon(o)

* Org mode for emacs
  :PROPERTIES:
  :CATEGORY: Org mode
  :Effort:   1:30
  :END:
*** TODO [#E] reproduce org mode effort bug
    SCHEDULED: <2010-10-25 Mon>
    :PROPERTIES:
    :Effort:   0:10
    :END:
    [2010-10-25 Mon]
*** TODO how to get list of all tags?
    SCHEDULED: <2010-10-25 Mon>
    :PROPERTIES:
    :Effort:   0:10
    :END:
*** TODO mark a task done-yesterday
    SCHEDULED: <2010-10-25 Mon>
    :PROPERTIES:
    :Effort:   0:10
    :END:
--------------------------   recurring.org  --------------------------
#+STARTUP: odd
#+STARTUP: hidestars
#+SEQ_TODO: TODO NEXT PENDING | DONE(d!) CANCELLED(c@)
#+TAGS: Rock(r) Frog(f)

* TODO Recurring
  :PROPERTIES:
  :CATEGORY: Recurring
  :END:
*** TODO krebs security blog
    SCHEDULED: <2010-10-25 Mon +1d>
    :PROPERTIES:
    :Effort:   0:10
    :END:
*** TODO read local paper
    SCHEDULED: <2010-10-25 Mon ++1d>
    :PROPERTIES:
    :Effort:   0:10
    :END:
*** TODO booktv check
    SCHEDULED: <2010-10-25 Mon +1w>
    :PROPERTIES:
    :Effort:   1:30
    :END:
-------------------------------------------------------------------   

Construct the agenda view by typing C-c a a while in buffer master.org.
Then in the agenda, type d for daily.

In the agenda, use the up/down arrow keys to move the highlight to the
task of interest, and press e, then use a digit to select the effort.

This example has made one thing clear to me - when I thought that 
setting the effort was not working, it was actually CHANGING THE EFFORT
FOR A DIFFERENT TASK.  The problem is usually observable when setting
the effort in the last three tasks in the agenda, the ones from
the recurring.org file, though sometimes (I think) those have worked
correctly.  The effort change for these last three tasks, when wrong,
will always be to one of the other tasks in recurring.org.

I hope this is sufficient.

An oddity in this example is that typing e also opens a second window 
in the frame (like when spacebar is typed).  Don't recall having seen
this happen before.

The priority setting problem is also observable, but one time only! On 
my first priority setting attempt with these files, I typed the comma 
while the first item in recurring was highlighted and got the:  

org-agenda-priority: Wrong type argument: integer-or-marker-p, nil

All further attempts worked properly.  Strange.