emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <eric.schulte@gmx.com>
To: Jacek Generowicz <jacek.generowicz@cern.ch>
Cc: emacs-orgmode@gnu.org
Subject: Re: Babel Python sessions severely broken
Date: Fri, 09 Mar 2012 14:24:34 -0700	[thread overview]
Message-ID: <87aa3psc19.fsf@gmx.com> (raw)
In-Reply-To: <d39ca420-b7f9-4750-9542-2a15606c92fb@CERNFE22.cern.ch> (Jacek Generowicz's message of "Fri, 9 Mar 2012 22:05:41 +0100")

Jacek Generowicz <jacek.generowicz@cern.ch> writes:

> At Fri, 9 Mar 2012 13:31:05 -0700,
> Eric Schulte wrote:
>> I look forward to upcoming patches.
> I've not dug around the implementation of babel before. Any pointers
> on where to start?


The best place to look at is existing lisp/ob-*.el files both for Python
itself and other languages.  These provide examples of how to deal with
nearly every session execution contingency.  The lisp/ob-comint.el file
provides functions which abstract away some of the hairy details of
working with session comint buffer.

Largely I would hope that you'll have to spend more time with the python
library which will be performing the evaluation, rather than with the
related Org-mode functions.

On the more general elisp dev side of things, one hint which I find
useful when exploring the workings of new code is edebug, which allows
single-stepping through the evaluation of a function.

Thanks, please do let me know if I can help with advice or explanation,

Eric Schulte

      reply	other threads:[~2012-03-09 21:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09 18:20 Jacek Generowicz
2012-03-09 20:31 ` Eric Schulte
2012-03-09 21:05   ` Jacek Generowicz
2012-03-09 21:24     ` Eric Schulte [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=87aa3psc19.fsf@gmx.com \
    --to=eric.schulte@gmx.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jacek.generowicz@cern.ch \
    --subject='Re: Babel Python sessions severely broken' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this 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).