emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Giacomo M <jackjackk@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Help with "alternative" ipython session workflow
Date: Sat, 11 Apr 2015 16:09:42 -0700	[thread overview]
Message-ID: <5529A9B6.1050901@gmail.com> (raw)

I have never been able to make org sessions getting along properly with 
ipython, so at the moment I'm using a sort of handmade hybrid between 
org and an ipython notebook, doing the following:
1. Enter the first source block in a .org file
2. Start an ipython instance with C-c C-c
3. Keep the org/src buffer and *Python* buffer side by side
4. Copy paragraph of code around cursor (keeping cursor in position) (I 
usually split sections of code I want to run individually with spaces)
5. Select *Python* buffer
6. Go to last position
7. Type %paste
8. Go back to other buffer (src/org)

I probably sound like a caveman doing this over and over, but this is 
the most stable setup I could find. Plus I keep experimenting w/ code, 
and this gives me a very interactive environment. Macros helped me to 
automatize steps 4-8, but still it's not very flexible, e.g. I need the 
side-by-side buffers, with ipython already running.

I was wondering whether anybody has any suggestions to improve this (and 
make me save some minutes of life every day), or any good reference to 
make ipython work smoothly with org src blocks



             reply	other threads:[~2015-04-11 23:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-11 23:09 Giacomo M [this message]
2015-04-12  1:59 ` Help with "alternative" ipython session workflow Ista Zahn
2015-04-12  2:54   ` Ken Mankoff

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=5529A9B6.1050901@gmail.com \
    --to=jackjackk@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).