unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Evaluate current line in Python mode?
Date: Mon, 30 Aug 2010 12:43:54 +0200	[thread overview]
Message-ID: <4C7B8B6A.6030906@easy-emacs.de> (raw)
In-Reply-To: <87iq2tu84v.fsf@tux.homenetwork>

Am 29.08.2010 10:37, schrieb Thierry Volpiatto:
> Andreas Röhler<andreas.roehler@easy-emacs.de>  writes:
>
>> Am 28.08.2010 21:45, schrieb Michael Hannon:
>>> Greetings.  I use Emacs for, among other things, running Python code and R
>>> code.  In both modes (Python and ESS "Emacs Speaks Statistics") there is a
>>> function bound to the sequence:
>>>
>>>       C-c C-n
>>>
>>> Both functions advance to the next line of code in the buffer, i.e., skipping
>>> blank lines, comment lines, etc.
>>>
>>> In ESS mode the function bound to C-c C-n also (by default) sends the current
>>> line to R for evaluation.  I find this to be very convenient as a way to watch
>>> calculations "evolve".
>>>
>>> It's possible to do something similar in Python mode by selecting the
>>> current line and then sending the region (C-c C-r) to Python for evaluation,
>>> but this is a bit cumbersome.
>>>
>>> Can anybody suggest a way to graft the ESS-mode behavior onto Python mode?
>>
>> Try this:
>>
>> (defun my-python-send-region (&optional beg end)
>>    (interactive)
>>    (let ((beg (cond (beg beg)
>>                     ((region-active-p)
>>                      (region-beginning))
>>                     (t (line-beginning-position))))
>>          (end (cond (end end)
>>                     ((region-active-p)
>>                      (copy-marker (region-end)))
>>                     (t (line-end-position)))))
>>      (python-send-region beg end)))
>>
>> HTH
>> Comments welcome
>
> Isn't it simpler:
>
> (defun my-python-send-region (beg end)
>    (interactive "r")
>    (if (eq beg end)
>        (python-send-region (point-at-bol) (point-at-eol))
>        (python-send-region beg end)))
>

"r" complains if no mark is set
Did choose the default getting rid of that constraint

> Otherwise, with cond you can write
>
> (cond (beg)
>        (end))
>
> instead of
>
> (cond (beg beg)
>        (end end))
>
>>

Indeed, will change this.

Thanks




>> Andreas
>>
>> --
>> https://code.launchpad.net/~a-roehler/python-mode
>> https://code.launchpad.net/s-x-emacs-werkstatt/
>>
>>> I've appended the high-level descriptions of both functions.  I understand
>>> that the source code is available, and that I'm free to hack away to my
>>> heart's content.  I just don't have the skills at Emacs/Lisp required to do
>>> such a thing in a finite amount of time.
>>>
>>> Thanks and best wishes,
>>>
>>> -- Mike
>>>
>>>
>>>       Python mode
>>>       ===========
>>>
>>> C-c C-n runs the command python-next-statement, which is an
>>> interactive compiled Lisp function.
>>>
>>> It is bound to C-c C-n.
>>>
>>> (python-next-statement&optional COUNT)
>>>
>>> Go to start of next statement.
>>> With argument COUNT, do it COUNT times.  Stop at end of buffer.
>>> Return count of statements left to move.
>>>
>>> ----------
>>>
>>>       ESS mode
>>>       ========
>>>
>>> C-c C-n runs the command ess-eval-line-and-step, which is an
>>> interactive compiled Lisp function in `ess-inf.el'.
>>>
>>> It is bound to C-c C-n, C-c C-e C-n,<menu-bar>   <ESS>   <ESS Eval>   <Eval
>>> line&   step>.
>>>
>>> (ess-eval-line-and-step&optional SIMPLE-NEXT EVEN-EMPTY INVISIBLY)
>>>
>>> Evaluate the current line visibly and step to the "next" line.
>>> "next" = the next line with non-comment code _unless_ SIMPLE-NEXT is non-nil,
>>> possibly via prefix arg.  If 2nd arg EVEN-EMPTY [prefix as well],
>>> also send empty lines.    When the variable `ess-eval-empty' is non-nil
>>> both SIMPLE-NEXT and EVEN-EMPTY are interpreted as true.
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>




  reply	other threads:[~2010-08-30 10:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-28 19:45 Evaluate current line in Python mode? Michael Hannon
2010-08-29  8:02 ` Andreas Röhler
2010-08-29  8:37   ` Thierry Volpiatto
2010-08-30 10:43     ` Andreas Röhler [this message]
2010-08-30 12:36       ` Thierry Volpiatto
2010-08-30 16:17         ` Andreas Röhler
     [not found] <mailman.3.1283024747.17543.help-gnu-emacs@gnu.org>
2010-08-28 20:10 ` Xah Lee
2010-08-28 23:49 ` TheFlyingDutchman

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C7B8B6A.6030906@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.
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).