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: Fri, 03 Jun 2011 21:07:13 -0700	[thread overview]
Message-ID: <87r57ap7da.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 877h92r9cg.fsf@ericabrahamsen.net

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> 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
> Aha, I did once try building emacs 24 on this machine, for the heck of
> it, and it's still hanging around under /usr/local/bin. I'm not sure how
> much work would be required to uproot it entirely, but I can give it a
> shot, particularly with the lisp libraries, and see if that makes a
> difference.
> Thanks for the hint,
> Eric

Nope, pretty sure I got it all out of there, and I'm still getting the
same error, and =with-output-to-temp-buffer= is definitely still a
c-source code function.

I re-installed emacs from the Ubuntu repositories for good measure, to
no avail. If I run emacs -Q so that the org code base that's loaded is
the default, the error disappears. Adding git org to the load path,
reloading org and trying again is enough to make the error return.

Running emacs -Q from the command line produces:

Warning: Lisp directory `/usr/local/share/emacs/23.2/site-lisp' does not exist.
Warning: Lisp directory `/usr/local/share/emacs/site-lisp' does not exist.

Which I've never seen before, and which seems like a warning sign. I'm
quite prepared to believe that I've somehow got tangled codebases, but I
really don't know where to look next…


  reply	other threads:[~2011-06-04  4:07 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 [this message]
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:

  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=87r57ap7da.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).