From: Nick Dokos <email@example.com>
To: Sean Lynch <firstname.lastname@example.org>
Cc: Jude DaShiell <email@example.com>, firstname.lastname@example.org
Subject: Re: Problem inserting date
Date: Tue, 13 Nov 2012 00:47:07 -0500 [thread overview]
Message-ID: <3987.1352785627@alphaville> (raw)
In-Reply-To: Message from Sean Lynch <email@example.com> of "Mon, 12 Nov 2012 20:15:35 EST." <50A19F37.firstname.lastname@example.org>
Sean Lynch <email@example.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
> error("Before first headline at position %d in buffer %s" 1 #<buffer
> byte-code("\300\301`p#\207" [error "Before first headline at position
> %d in buffer %s"] 4)
> org-add-planning-info(deadline nil closed)
> 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.
prev parent reply other threads:[~2012-11-13 5:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 18:19 Problem inserting date Sean Lynch
2012-11-12 23:13 ` Jude DaShiell
2012-11-12 23:28 ` Sean Lynch
2012-11-12 23:44 ` Jude DaShiell
2012-11-12 23:55 ` Nick Dokos
2012-11-13 1:15 ` Sean Lynch
2012-11-13 3:10 ` Jude DaShiell
2012-11-13 5:47 ` Nick Dokos [this message]
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).