From: "Thomas S. Dye" <tsd@tsdye.com>
To: William Henney <whenney@gmail.com>
Cc: Karl Voit <news1142@karl-voit.at>, emacs-org <emacs-orgmode@gnu.org>
Subject: Re: Mixing Python2 and Python3 blocks in one file
Date: Tue, 17 May 2016 23:42:51 -0400 [thread overview]
Message-ID: <m2vb2c58w4.fsf@tsdye.com> (raw)
In-Reply-To: <CAKchnZNra2jvy=ta9OofeWp2V5sUwLm0oy2fHb2BUp5AdEYPpQ@mail.gmail.com>
William Henney writes:
>> Cool, I did not find this parameter yet.
>>
>> Is this undocumented? http://orgmode.org/org.html does not contain
>> the string ":python:" and
>> http://orgmode.org/org.html#Language_002dspecific-header-arguments
>> also does not mention this parameter.
>>
>>
> It is documented at
> http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-python.html
As of a few hours ago, when I added it. It probably wasn't there when
Karl looked.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2016-05-18 3:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 8:31 Mixing Python2 and Python3 blocks in one file Karl Voit
2016-05-08 15:13 ` Karl Voit
2016-05-17 14:24 ` William Henney
2016-05-17 14:54 ` Karl Voit
2016-05-17 15:37 ` John Kitchin
2016-05-18 1:19 ` William Henney
2016-05-18 3:42 ` Thomas S. Dye [this message]
2016-05-18 7:11 ` Karl Voit
2016-05-18 7:10 ` Division of Org documentation: Org manual and Worg (was: Mixing Python2 and Python3 blocks in one file) Karl Voit
2016-05-18 8:10 ` Division of Org documentation: Org manual and Worg Daniele Pizzolli
2016-05-18 9:03 ` Rasmus
2016-05-18 10:08 ` Daniele Pizzolli
2016-05-18 10:18 ` Rasmus
2016-05-20 17:15 ` Daniele Pizzolli
2016-05-20 18:46 ` Rasmus
2016-05-18 10:18 ` Daniele Pizzolli
2016-05-18 13:45 ` Mixing Python2 and Python3 blocks in one file Ken Mankoff
2016-05-19 3:37 ` William Henney
2016-05-19 13:18 ` Ken Mankoff
2016-05-19 19:21 ` William Henney
2016-05-19 19:32 ` Ken Mankoff
2016-05-19 20:01 ` William Henney
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2vb2c58w4.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=news1142@karl-voit.at \
--cc=whenney@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.