From: Nick Dokos <nicholas.dokos@hp.com>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>,
nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: export problems
Date: Fri, 03 Jun 2011 11:30:03 -0400 [thread overview]
Message-ID: <8379.1307115003@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Nick Dokos <nicholas.dokos@hp.com> of "Fri, 03 Jun 2011 11:24:13 EDT." <8300.1307114653@alphaville.dokosmarshall.org>
Nick Dokos <nicholas.dokos@hp.com> wrote:
> Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>
> > It was while trying to produce a backtrace (with edebug) that I
> > discovered that re-evaluating the code fixed the problem. I set
> > debug-on-error to t and reproduced the error, which gave me this:
> >
> > Debugger entered--Lisp error: (error "Cannot return from the debugger in an error")
> > internal-temp-output-buffer-show(#<buffer *Org Export/Publishing Help*>)
> > org-export(nil)
> > call-interactively(org-export nil nil)
> >
> > Presumably this isn't really what's needed -- can you provide a pointer
> > to producing a more useful backtrace?
> >
>
> Only the usual suspects: you are loading uncompiled code I hope? I don't
> even have the function in either of my emacsen (24.0.50 and 23.1.1):
> does C-h f internal-temp-output-buffer-show RET show anything in yours?
>
Duh - of course not: that's the error you get. Never mind.
Nick
next prev parent reply other threads:[~2011-06-03 15:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 4:02 export problems Eric Abrahamsen
2011-06-03 6:13 ` Noorul Islam
2011-06-03 14:08 ` Eric Abrahamsen
2011-06-03 14:23 ` Nick Dokos
2011-06-03 15:08 ` Eric Abrahamsen
2011-06-03 15:24 ` Nick Dokos
2011-06-03 15:30 ` Nick Dokos [this message]
2011-06-03 15:55 ` Nick Dokos
2011-06-03 19:41 ` Eric Abrahamsen
2011-06-04 4:07 ` Eric Abrahamsen
2011-06-06 17:58 ` Eric Abrahamsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8379.1307115003@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=eric@ericabrahamsen.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.