From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Evaluating python code blocks in python-mode
Date: Sun, 21 Jun 2015 08:20:46 +0200 [thread overview]
Message-ID: <558657BE.5090207@easy-emacs.de> (raw)
In-Reply-To: <5585BA55.8090205@easy-emacs.de>
Am 20.06.2015 um 21:09 schrieb Andreas Röhler:
>
> Am 20.06.2015 um 12:50 schrieb Yuri D'Elia:
>> Hi everyone,
>>
>> I'd like some advice about using python-mode with a python subprocess.
>> I always preferred to use emacs+file+external process as opposed to use
>> an ipython's notebook-like interface: it's just more convenient,
>> especially when debugging existing code.
>>
>> I often use the same setup when doing some analysis, and this is when an
>> inotebook-like interface is more convenient for evaluation: I'd like to
>> evaluate code not line-by-line, or by defun, but by my custom-defined
>> blocks. I realized I was continuously selecting a region, and using
>> py-send-region over and over.
>>
>> Right now I narrow to the region I'm editing, and use py-send-buffer
>> instead. It's ok-eish, but narrow/widen narrow/widen, while less common,
>> is still inconvenient.
>>
>> I've seen people using org-mode for this kind of setup instead. Which
>> might be ok, but I'd like to know what other choices I could have as
>> well.
>>
>> I was thinking of defining a custom region using comments, and defining
>> my own py-send-custom-block using comment markers as boundaries. Surely,
>> something like this must already exists.
>>
>>
>
>
> IIUC in question are arbitrary chunks of code.
> What about something like that:
>
> ;;;;
>
> (defvar py-section-start "# {{")
> (defvar py-section-end "# }}")
>
> (defun py-send-section ()
> (interactive)
> (save-excursion
> (unless (looking-at py-section-start)
> (search-backward py-section-start)
> (set-mark (point))
> (if (and (looking-at py-section-start)(search-forward
> py-section-end))
> (py-execute-region (region-beginning) (region-end))
> (error "Can't see boundaries of py-section")))))
>
> ;;;;
>
> BTW didn't call it block, as this is already used by forms heading
> others.
>
>
>
As python-mode sends a plain string to interpreter anyway, must not
touch mark in buffer:
(defun py-send-section ()
(interactive)
(save-excursion
(let ((start (progn (unless (looking-at py-section-start)
(search-backward py-section-start)
(point)))))
(if (and (looking-at py-section-start)(search-forward
py-section-end))
(py-execute-region start (point))
(error "Can't see boundaries of py-section")))))
next prev parent reply other threads:[~2015-06-21 6:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 10:50 Evaluating python code blocks in python-mode Yuri D'Elia
2015-06-20 19:09 ` Andreas Röhler
2015-06-21 6:20 ` Andreas Röhler [this message]
2015-06-21 16:17 ` Yuri D'Elia
2015-06-21 16:18 ` Yuri D'Elia
2015-06-21 16:35 ` Yuri D'Elia
2015-06-21 18:52 ` Andreas Röhler
2015-06-25 10:25 ` Yuri D'Elia
2015-06-25 10:25 ` Yuri D'Elia
2015-06-25 11:21 ` Andreas Röhler
2015-06-25 12:33 ` Yuri D'Elia
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=558657BE.5090207@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--cc=help-gnu-emacs@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 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.