From: Nick Dokos <nicholas.dokos@hp.com>
To: David Lee <zhushenli2@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: schedule/deadline and ido-mode conflict
Date: Wed, 12 May 2010 22:26:51 -0400 [thread overview]
Message-ID: <10401.1273717611@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from David Lee <zhushenli2@gmail.com> of "Thu, 13 May 2010 09:49:27 +0800." <4BEB5AA7.9080305@gmail.com>
David Lee <zhushenli2@gmail.com> wrote:
> On 05/12/2010 11:46 PM, Nick Dokos wrote:
> > David Lee<zhushenli2@gmail.com> wrote:
> >
> >
> >> After insert schedule and deadline by C-c C-s, C-c C-d, I switch
> >> buffer by ido-mode command ido-switch-buffer.
> >>
> >> Emacs will give out a message:
> >> Error in post-command-hook: (void-variable org-ans1)
> >>
> >> And ido-switch-buffer doesn't work.
> >>
> >> My environment: Emacs 23.1, Org-mode 6.36.
> >>
> >
> > Please post a backtrace. To find out how to get a backtrace, read
> > section 1.4, "Feedback", of the Org manual.
> >
>
> I turn on "Enter Debugger On error" all the time, and follow the
> instruction in Org Info.
> But I cannot get the backtrace, seems its not an *error* (didn't fire
> up elisp debugger), but just a message?
>
> The conflict make me give up schedule/deadline.
>
> So, any other suggestion on get the backtrace?
>
Nope - no ideas/suggestions: seems to me it should have triggered.
What's the value of post-command-hook just before you get the error?
Note that that's a buffer-local variable, so you'll have to evaluate it
(using `C-h v post-command-hook <RET>') in the correct buffer.
Nick
next prev parent reply other threads:[~2010-05-13 3:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 15:40 schedule/deadline and ido-mode conflict David Lee
2010-05-12 15:46 ` Nick Dokos
2010-05-13 1:49 ` David Lee
2010-05-13 2:26 ` Nick Dokos [this message]
2010-05-13 3:04 ` David Lee
2010-05-14 8:27 ` UPDATE " David Lee
2010-05-14 11:33 ` Carsten Dominik
2010-10-12 8:57 ` Antoine Levitt
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10401.1273717611@gamaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=zhushenli2@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).