Sean Lynch <lynchse...@gmail.com> wrote:
> >
> C-c C-d is bound to org-deadline as it should be. I was thinking that I
> might have something wacky in my setup that is screwing this up, but I
> haven't found anything so far.
> >
> > You should be able to get a backtrace then by doing M-x
> > toggle-debug-on-error
> > and retrying the problematic command.
> >
> I get the following backtrace:
>
> Debugger entered--Lisp error: (error "Before first headline at position
> 1 in buffer org-test.org")
> signal(error ("Before first headline at position 1 in buffer
> org-test.org"))
> error("Before first headline at position %d in buffer %s" 1 #<buffer
> org-test.org>)
> byte-code("\300\301`p#\207" [error "Before first headline at position
> %d in buffer %s"] 4)
> org-back-to-heading(t)
> ...
> org-add-planning-info(deadline nil closed)
> org-deadline(nil)
> call-interactively(org-deadline nil nil)
>
>
> Also... I just found something very interesting with this behaviour that
> will probably help debug this.
>
> If I have a frame with two windows split horizontally (two windows
> side-by-side with C-x 3) with one window containing the org file I get
> this error
>
> If I have a frame with only one window containing the org file,
> everything works fine.
>
> If I have a frame with two windows split vertically (one above the other
> with C-x 2) with one window containing the org file, everything works fine.
>
>
Sorry, I still can't reproduce it. The backtrace is consistent with
point being before the first headline, but not with point being at the
end of the first second-level headline.
Nick
