From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: Fwd: run python from org, draft Date: Fri, 29 Mar 2013 10:59:49 -0600 Message-ID: <871uayrvju.fsf@gmail.com> References: <5154BC51.1050001@easy-emacs.de> <5155A97D.2090907@easy-emacs.de> <87sj3e6y5n.fsf@gmail.com> <5155B346.3060708@easy-emacs.de> <87ehey6upd.fsf@gmail.com> <5155C611.5000104@easy-emacs.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:59581) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ULcev-0002Wm-TH for emacs-orgmode@gnu.org; Fri, 29 Mar 2013 13:00:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ULcet-0000PR-Te for emacs-orgmode@gnu.org; Fri, 29 Mar 2013 13:00:09 -0400 Received: from mail-pd0-f177.google.com ([209.85.192.177]:50601) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ULcet-0000PE-OF for emacs-orgmode@gnu.org; Fri, 29 Mar 2013 13:00:07 -0400 Received: by mail-pd0-f177.google.com with SMTP id y14so325333pdi.22 for ; Fri, 29 Mar 2013 10:00:06 -0700 (PDT) In-Reply-To: <5155C611.5000104@easy-emacs.de> ("Andreas =?utf-8?Q?R=C3=B6h?= =?utf-8?Q?ler=22's?= message of "Fri, 29 Mar 2013 17:49:21 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Andreas =?utf-8?Q?R=C3=B6hler?= Cc: emacs-orgmode , Gary Oberbrunner Andreas R=C3=B6hler 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 f= rom 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 ha= ve 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 --=20 Eric Schulte http://cs.unm.edu/~eschulte