From: Eric Schulte <schulte.eric@gmail.com>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
Gary Oberbrunner <garyo@oberbrunner.com>
Subject: Re: Fwd: run python from org, draft
Date: Fri, 29 Mar 2013 10:59:49 -0600 [thread overview]
Message-ID: <871uayrvju.fsf@gmail.com> (raw)
In-Reply-To: <5155C611.5000104@easy-emacs.de> ("Andreas Röhler"'s message of "Fri, 29 Mar 2013 17:49:21 +0100")
Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
> Am 29.03.2013 17:20, schrieb Eric Schulte:
>
>> A valid opinion, in fact I think I defended that point of view myself,
>
> Hi Eric,
>
> so, if I'm saying: let's make things considerably easier, working right from the spot,
> why not try that?
>
> What I need still is a specification, what :session and the other header arguments shall do.
> Presently they do quite different things. Also can't read a bulk of mails to figure out some guessing.
>
> Please write a specification and with the help of the other guys let's have some tiny and
> effective ob-python.
>
Sorry, I'm not going to do this work for you. If you want to take a
shot at re-working ob-python, then you're welcome to. However, I would
recommend first reading through some of the history which lead to its
current state, and fully understanding what that current state is (which
at a minimum means reading and digesting the relevant documentation).
> Let's see of we need more lines than ob-emacs-lisp.el :)
>
You will. :)
Best of luck,
>
> Cheers
--
Eric Schulte
http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2013-03-29 17:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 21:55 run python from org, draft Andreas Röhler
[not found] ` <CAFChFyjZyxcnH1_jSWEUgXNkvJ0c3F8f4ojQa_EtPov2TjtziQ@mail.gmail.com>
2013-03-29 12:11 ` Fwd: " Gary Oberbrunner
2013-03-29 14:47 ` Andreas Röhler
2013-03-29 14:57 ` John Hendy
2013-03-29 15:09 ` Eric Schulte
2013-03-29 15:29 ` Andreas Röhler
2013-03-29 16:20 ` Eric Schulte
2013-03-29 16:49 ` Andreas Röhler
2013-03-29 16:59 ` Eric Schulte [this message]
2013-03-29 18:33 ` Evan Misshula
2013-03-29 18:50 ` Eric Schulte
2013-03-29 19:04 ` Evan Misshula
[not found] ` <CAFChFyhRbz6hh-NyOZTfdKJcTPh=F3J=07k2fR9p+A9Wig_pRA@mail.gmail.com>
2013-03-29 20:10 ` Fwd: " Gary Oberbrunner
2013-03-29 20:58 ` Andreas Röhler
2013-03-31 20:04 ` Gary Oberbrunner
2013-03-29 15:35 ` John Hendy
[not found] ` <CAFChFyhOrPVS2E5CE9H2+zX5TFV4D-themQbjx2DaSx-WmG14g@mail.gmail.com>
2013-03-29 20:11 ` Fwd: " Gary Oberbrunner
2013-03-29 15:50 ` John Hendy
2013-03-29 16:23 ` Eric Schulte
2013-03-29 16:47 ` Eric Schulte
2013-03-29 19:06 ` Andreas Röhler
2013-03-29 20:04 ` Andreas Röhler
2013-03-29 19:59 ` Gary Oberbrunner
2013-03-29 20:15 ` Andreas Röhler
2013-03-29 20:25 ` Eric Schulte
2013-03-29 20:45 ` Gary Oberbrunner
2013-03-29 21:13 ` Eric Schulte
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=871uayrvju.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=andreas.roehler@easy-emacs.de \
--cc=emacs-orgmode@gnu.org \
--cc=garyo@oberbrunner.com \
/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).