From: "Ondřej Grover" <ondrej.grover@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Proposal and RFC for improving ob-python
Date: Tue, 8 Dec 2015 08:43:33 +0100 [thread overview]
Message-ID: <CAOyjJOLnC=XVXqEpH1YRUcDL6E5eGN-rC3A+yfswCS1U5o+_pw@mail.gmail.com> (raw)
In-Reply-To: <874mfut35p.fsf@kyleam.com>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
Hello,
thank you all for confirming that I'm in the right place. If I felt
confident enough that this would work, I wold have already presented a
patch (I'm not an experienced ELisp programmer). That's why I want to
discuss this approach first.
Kyle, I'll be grateful for you feedback.
Kind regards,
Ondřej Grover
On Mon, Dec 7, 2015 at 9:27 PM, Kyle Meyer <kyle@kyleam.com> wrote:
> Hi Ondřej,
>
> Ondřej Grover <ondrej.grover@gmail.com> writes:
>
> > TL;DR for those that may have been scared off by the length of my
> previous
> > email:
> > I propose a method of improving ob-python.el by using a progn-like eval()
> > Python function which can wrap and execute source blocks.
> >
> > If this list is not appropriate for discussion of improvements to
> > ob-python.el, could you please give me pointers how to reach people that
> > might be interested in helping and discussing?
>
> Thanks for your proposal. This is the right place to discuss it. I've
> only had the chance to briefly look at this, but I'll try to take a
> closer look soon.
>
> --
> Kyle
>
[-- Attachment #2: Type: text/html, Size: 1625 bytes --]
next prev parent reply other threads:[~2015-12-08 7:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 19:22 Proposal and RFC for improving ob-python Ondřej Grover
2015-12-07 20:27 ` Kyle Meyer
2015-12-08 7:43 ` Ondřej Grover [this message]
2015-12-07 20:36 ` Thomas S. Dye
2015-12-07 20:51 ` Achim Gratz
-- strict thread matches above, loose matches on Subject: below --
2015-12-10 7:47 Ondřej Grover
2015-12-11 3:39 ` Kyle Meyer
2015-12-05 17:17 Ondřej Grover
2015-12-10 7:22 ` Kyle Meyer
2016-08-29 12:53 ` Greg Minshall
2016-08-30 19:17 ` John Kitchin
2016-08-31 2:44 ` Greg Minshall
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='CAOyjJOLnC=XVXqEpH1YRUcDL6E5eGN-rC3A+yfswCS1U5o+_pw@mail.gmail.com' \
--to=ondrej.grover@gmail.com \
--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).