emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Dr. Volker Zell" <dr.volker.zell@oracle.com>
Cc: sperber@deinprogramm.de, emacs-orgmode@gnu.org
Subject: Re: org-babel and Xemacs incompatibilities
Date: Tue, 25 May 2010 18:26:37 -0600	[thread overview]
Message-ID: <877hmrmrsy.fsf@gmail.com> (raw)
In-Reply-To: <7zsk5g9mph.fsf@vzell-de.de.oracle.com> (Volker Zell's message of "Tue, 25 May 2010 14:42:50 +0200")

More replies,

"Dr. Volker Zell" <dr.volker.zell@oracle.com> writes:

>>>>>> Volker Zell writes:
>
>>>>>> Eric Schulte writes:
[...]
> And two more
>
>  o Symbol's function definition is void: assoc-default when trying to display an image
>

This is actually an issue in the core of org-mode as `assoc-default' is
called by `org-open-at-point'.  I'm not sure how Carsten would want to
handle this.  The `assoc-default' function is pretty simple and could be
coppied into org-mode.  Again I don't know how these xemacs
compatibility issues are normally handled.

>  o Symbol's function definition is void: make-temp-file when using org-babel-dot
>  

Hmm, `make-temp-file' is used throughout pretty much all of the
org-babel language specific files.  Maybe we should just copy this
function directly into org-babel.  This seems like commonly useful
functionality, I wonder how other xemacs packages handle similar
requirements.

Sorry I'm not much help here, these fixes should be straightforward once
the "best practices" for xemacs compatibility is known.

Thanks -- Eric

  reply	other threads:[~2010-05-26  3:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-11  9:09 org-babel and Xemacs incompatibilities Dr. Volker Zell
2010-05-17 23:17 ` Eric Schulte
2010-05-25 11:16   ` Dr. Volker Zell
2010-05-25 12:42     ` Dr. Volker Zell
2010-05-26  0:26       ` Eric Schulte [this message]
2010-06-07 13:04         ` Michael Sperber
2010-05-25 23:36     ` Eric Schulte
2010-06-07 12:48       ` Michael Sperber

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=877hmrmrsy.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=dr.volker.zell@oracle.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sperber@deinprogramm.de \
    /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).