emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: export problems
Date: Mon, 06 Jun 2011 10:58:31 -0700	[thread overview]
Message-ID: <87ei36on94.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 8796.1307116531@alphaville.dokosmarshall.org

Nick Dokos <nicholas.dokos@hp.com> writes:

> 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?
> I see some messages about internal-temp-output-buffer-show when
> googling: they seem related to Stefan Monnier's effort to make
> with-output-to-temp-buffer a Lisp macro (rather than a special form in C
> code, IIUC) - but this seems to be bleeding edge stuff, not 23.2. Are
> you perhaps picking up emacs bits and pieces from places you shouldn't?
> Maybe Stefan (cc:ed) has some ideas.
> Nick

Grepping for "internal-temp-output-buffer-show" in my org directory
gives me this:

Binary file ./lisp/org.elc matches
Binary file ./lisp/org-bibtex.elc matches
Binary file ./lisp/org-entities.elc matches
Binary file ./lisp/org-exp.elc matches
Binary file ./lisp/org-attach.elc matches
Binary file ./lisp/org-table.elc matches
Binary file ./lisp/org-agenda.elc matches
Binary file ./lisp/org-clock.elc matches

Only compiled files! It makes sense now that re-evaluating the source
code fixes the problems. In the Makefile I changed:




And after I ran "make all" again everything worked fine. I have no other
"emacs" executables anywhere on my system, so far as I can tell, though
I guess it's inevitable that this is some kind of holdover from my
previous experiments with emacs trunk.

Anyway, problem very close to solved…


      parent reply	other threads:[~2011-06-06 17:58 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
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 [this message]

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:

  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=87ei36on94.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=emacs-orgmode@gnu.org \


* 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).