Hi Guys,
Thanks for trying to help me with this.
I re-did the installation:
I ran M-x load-library org followed by M-x org-version - which
returned 7.8.09.
(Incidentally, and for the sake of completeness in this report, I
built the compiled version of this upgrade by using
M-x cd ~/.emacs.d/org-7.8.09/ followed by C-u 0 M-x
byte-recompile-directory)
I renamed the org-6.36 folder. I started up emacs and the error still
appeared.
Prior to the attempted upgrade, my load-path contained:
(add-to-list 'load-path "~/.emacs.d/org-6.36/lisp")
(add-to-list 'load-path "~/.emacs.d/org-6.36/contrib/lisp")
And after the attempted upgrade my load-path contained:
(add-to-list 'load-path "~/.emacs.d/org-7.8.09/lisp")
(add-to-list 'load-path "~/.emacs.d/org-7.8.09/contrib/lisp")
As an experiment, I modified the load-path to consist only of one statement:
(add-to-list 'load-path "~/.emacs.d/org-7.8.09/")
; (add-to-list 'load-path "~/.emacs.d/org-7.8.09/contrib/lisp")
And suddenly the "bug" vanished. What's going on - do you have any idea?
I thought I would certainly need this
directory "~/.emacs.d/org-7.8.09/contrib/lisp" in my load-path.
I also tried some of the steps listed in:
http://orgmode.org/worg/org-contrib/org-track.html but when I execute
the command (listed there): M-x customize-variable RET org-track-directory
RET, I get the message [No Match] - so there apparently is not
org-track-directory variable (at least on windows)
Any ideas? Thanks in advance for your help.
-Fritz Kunze
On Tue, Apr 24, 2012 at 4:45 AM, Mike McLean <mike.mcl...@pobox.com> wrote:
>
> On Apr 23, 2012, at 7:15 PM, Bastien wrote:
>
> > fkunze <fku...@gmail.com> writes:
> >
> >> When I open an org file with #+startup: indent in the header, the
> cursor
> >> immediately goes to the bottom of the buffer and can not be moved
> upward.
> >
> > I can't reproduce this error...
> >
> >> This behavior does not occur in Org 6.36.
> >
> > ... and that's surely why.
>
> Actually he/she said that he had just upgraded to Org 7.8.09 (the test on
> 6.36 was his/her regression test) -- so I don't think the absolute version
> of Org is the problem.
>
> Fkunze - I am suspecting that you have mis-matched org-mode installs, i.e.
> pieces and parts of both. What does =M-x org-version= say when you are
> experiencing the problem?
>
> Can you completely clean/remove the old Org 6.36 version to ensure no
> conflict?
>
>
>
