orgmode opening source file from agenda when marking as done

orgmode opening source file from agenda when marking as done

[Michael Gilbert]

Hi all --

I seem to have mysteriously flipped some setting or other. Now,  
whenever I set a repeating item in my agenda as done, orgmode opens up  
the source file with that item in it, in a split frame. I have no idea  
why or what I'm supposed to do with that, but it sure slows down my  
workflow. Any tips on what's happening here?

-- Michael

Michael C. Gilbert -- mcg@gilbert.org

    The Gilbert Center -- http://gilbert.org
    Nonprofit Online News -- http://nonprofitnews.org

        "There can be no joy of life without joy of work." -- Aquinas

Re: orgmode opening source file from agenda when marking as done

[Matt Lundin]

Michael Gilbert <mcg@gilbert.org> writes:

> Hi all --
>
> I seem to have mysteriously flipped some setting or other. Now,
> whenever I set a repeating item in my agenda as done, orgmode opens up
> the source file with that item in it, in a split frame. I have no idea
> why or what I'm supposed to do with that, but it sure slows down my
> workflow. Any tips on what's happening here?

Are you seeing the source file every time you move to a new item in the
agenda view? One possibility here is that you turned on follow mode in
the agenda by hitting "f". 

Best,
Matt

Re: orgmode opening source file from agenda when marking as done

[Michael Gilbert]

On Aug 17,2009, at 10:27 AM, Matt Lundin wrote:

>> I seem to have mysteriously flipped some setting or other. Now,
>> whenever I set a repeating item in my agenda as done, orgmode opens  
>> up
>> the source file with that item in it, in a split frame. I have no  
>> idea
>> why or what I'm supposed to do with that, but it sure slows down my
>> workflow. Any tips on what's happening here?
>
> Are you seeing the source file every time you move to a new item in  
> the
> agenda view? One possibility here is that you turned on follow mode in
> the agenda by hitting "f".

Thank you. I double checked that and the answer is NO. Follow mode is  
off.

It only happens with repeating tasks. And it occurs not when I hit 't'  
but when I make the specific selection afterwards. The actual split  
windows that open make no real sense to me. Sometimes it looks like  
note taking for the item. Sometimes something else. I think I was just  
hoping this was something obvious.

Any other ideas?

-- Michael

Michael C. Gilbert -- mcg@gilbert.org

    The Gilbert Center -- http://gilbert.org
    Nonprofit Online News -- http://nonprofitnews.org

        "There can be no joy of life without joy of work." -- Aquinas

Re: Re: orgmode opening source file from agenda when marking as done

[Samuel Wales]

A long shot: check the value of your after todo state change hook.

-- 
Myalgic encephalomyelitis causes death (Jason et al. 2006)
and severe suffering.  Conflicts of interest are destroying
research. What people "know" is wrong. Silence = death.
http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm

Re: Re: orgmode opening source file from agenda when marking as done

[Michael Gilbert]

On Aug 17,2009, at 12:31 PM, Samuel Wales wrote:

> A long shot: check the value of your after todo state change hook.

Sorry. Noob still. What does that mean?

-- M

Re: Re: orgmode opening source file from agenda when marking as done

[Samuel Wales]

org-after-todo-state-change-hook is a variable defined in `org.el'.

-- 
Myalgic encephalomyelitis causes death (Jason et al. 2006)
and severe suffering.  Conflicts of interest are destroying
research. What people "know" is wrong. Silence = death.
http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm

Re: Re: orgmode opening source file from agenda when marking as done

[John Rakestraw]

Hi Michael --

> On Aug 17,2009, at 12:31 PM, Samuel Wales wrote:
> 
> > A long shot: check the value of your after todo state change hook.
> 
> Sorry. Noob still. What does that mean?
> 
> -- M

I agree that this is a long shot, but I think he was suggesting that
you check the "org-after-todo-state-change-hook" to see if it's been
changed from the default, which is nil.

You can check this in emacs this way --

C-h v org-after-todo-state-change-hook <enter>

When I do this in my emacs session I get this:

**
org-after-todo-state-change-hook is a variable defined in `org.el'.
Its value is nil

Documentation:
Hook which is run after the state of a TODO item was changed.
The new state (a string with a TODO keyword, or nil) is available in the
Lisp variable `state'.

You can customize this variable.
**

The question is whether you also get "Its value is nil"

--John

-- 
John Rakestraw

Re: Re: orgmode opening source file from agenda when marking as done

[Michael Gilbert]

On Aug 17,2009, at 1:16 PM, Samuel Wales wrote:

> org-after-todo-state-change-hook is a variable defined in `org.el'.

Thank you, John for the detailed explanation. Thank you, Samuel, for  
this help.

The value, alas, is nil.

Other ideas?

-- M

Re: Re: orgmode opening source file from agenda when marking as done

[Nick Dokos]

Michael Gilbert <mcg@gilbert.org> wrote:

> On Aug 17,2009, at 1:16 PM, Samuel Wales wrote:
> 
> > org-after-todo-state-change-hook is a variable defined in `org.el'.
> 
> Thank you, John for the detailed explanation. Thank you, Samuel, for  
> this help.
> 
> The value, alas, is nil.
> 
> Other ideas?
> 

So this is a persistent state of affairs? You restart emacs from scratch
and it still does it? If that's the case, then one of your
initialization files must have been modified - check modification dates,
compare against backups - by hook or crook, find what changed.

If that still does not produce results, you can bisect your way to the
place where the problem appears: start emacs with the -q switch and load
.emacs piecemeal: open the .emacs file in a buffer and evaluate it one
s-expr at a time by placing the cursor after the closing paren of the
s-expr and using C-x C-e (that is bound to eval-last-sexp).  Or if you
prefer bigger bites, mark a region and use M-x eval-region on it. Try
the agenda commands that give you trouble after every evaluation.  At
the beginning, you are going to get errors, since org-mode will not even
have been loaded. At some point, the agenda command is going to succeed
and either behave properly or misbehave - but then you know which part
of the initialization file is responsible and you can concentrate your
efforts on that.

You may also find that the problem arises when your .emacs loads another
initialization file, in which case you go through the same process on
that file. Eventually, you'll find the culprit.

HTH,
Nick

PS. It might be a good idea to post a more detailed description of
*exactly* what you are doing and what you see when the misbehavior
occurs. Although I read the thread completely, I'm still not quite sure
what exactly you are seeing - for example, could it be just the "note"
behavior of the org-log-done variable? (C-h v org-log-done <RET> for
details).  Taking a screenshot of emacs and posting that might help as
well.