emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Sperber <sperber@deinprogramm.de>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Dan Davison <davison@stats.ox.ac.uk>,
	mailing-list-org-mode Mode <emacs-orgmode@gnu.org>,
	"Dr. Volker Zell" <Dr.Volker.Zell@oracle.com>
Subject: Re: Xemacs incompatibilities
Date: Mon, 17 May 2010 16:39:18 +0200	[thread overview]
Message-ID: <y9l632mvbhl.fsf@deinprogramm.de> (raw)
In-Reply-To: <DE9B7177-AA8A-473D-A4C1-FB06689967E0@gmail.com> (Carsten Dominik's message of "Fri, 14 May 2010 14:40:53 +0200")


Carsten Dominik <carsten.dominik@gmail.com> writes:

> This is a really non-standard way for a mode definition which I guess
> should be fixed in XEmacs.  I have made that change anyway.  Eric or
> Dan, please note this change I made in the Babel sources.

As someone else pointed out, python-mode.el is something different from
python.el:

https://launchpad.net/python-mode

In particular, fixing the require won't be enough: org-babel-python.el
uses `run-python' and interacts with the inferior Python, whereas
python-mode.el defines `py-shell'.

Should I try to abstract over the differences?

>> 3.)
>>
>> When editing a src block with C-c ' in a temporary buffer in it's
>> native mode and then switching back with C-c ' to the original org
>> file, whenever I try to save a file with C-x C-s (not only the org
>> file) I'll get the message
>>
>>   This is not a sub-editing buffer, something is wrong...

Could you provide a little bit more context on what you did?  I'm not
very familiar with org-src (which I assume this is about), so a
step-by-step recipe would help me greatly.

-- 
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla

  parent reply	other threads:[~2010-05-17 14:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-11  9:04 Xemacs incompatibilities Dr. Volker Zell
2010-05-14 12:40 ` Carsten Dominik
2010-05-15 10:09   ` Leo
2010-05-17 14:39   ` Michael Sperber [this message]
2010-05-17 14:46     ` Carsten Dominik
2010-05-17 18:47       ` Dan Davison
2010-05-20  2:41         ` Dan Davison
2010-05-24 14:22       ` Michael Sperber
2010-05-20 16:31     ` Dr. Volker Zell
2010-05-24  8:39       ` PATCH: " Michael Sperber
2010-05-24 13:23         ` Dan Davison
2010-05-24  8:41       ` PATCH: Fix minor XEmacs compatibility issue 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=y9l632mvbhl.fsf@deinprogramm.de \
    --to=sperber@deinprogramm.de \
    --cc=Dr.Volker.Zell@oracle.com \
    --cc=carsten.dominik@gmail.com \
    --cc=davison@stats.ox.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    /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).