On 19.06.2014 15:40, Eric Schulte wrote:
Andreas Röhler writes:
On 18.06.2014 15:59, Eric Schulte wrote:
Shiyuan writes:
Hi all,
I found a solution to fix the echo problem of the emacs python shell:
http://stackoverflow.com/questions/8060609/python-interpreter-in-emacs-repeats-line
Andreas Röhler writes:
> On 18.06.2014 15:59, Eric Schulte wrote:
>> Shiyuan writes:
>>
>>> Hi all,
>>>I found a solution to fix the echo problem of the emacs python shell:
>>> http://stackoverflow.com/questions/8060609/python-interpreter-in-emacs-repeats-lines
>>>
>>> That is, in the In
On 18.06.2014 15:59, Eric Schulte wrote:
Shiyuan writes:
Hi all,
I found a solution to fix the echo problem of the emacs python shell:
http://stackoverflow.com/questions/8060609/python-interpreter-in-emacs-repeats-lines
That is, in the Interior Python buffer, do
M-: (setq comint-proces
> Hi Guys,
>
> please permit a comment after some times - it's just not to create
> heroes :)
>
> IMHO the complexity orb-babel took by creating its own slots for
> symbols like function names, variables etc. is not to handle reliably
> across the languages.
>
I don't understand what you mean by
Shiyuan writes:
> Hi all,
> I found a solution to fix the echo problem of the emacs python shell:
> http://stackoverflow.com/questions/8060609/python-interpreter-in-emacs-repeats-lines
>
> That is, in the Interior Python buffer, do
> M-: (setq comint-process-echoes t) ;; or nil
>
> Now, if
On 17.06.2014 08:21, Shiyuan wrote:
Hi all,
I found a solution to fix the echo problem of the emacs python shell:
http://stackoverflow.com/questions/8060609/python-interpreter-in-emacs-repeats-lines
That is, in the Interior Python buffer, do
M-: (setq comint-process-echoes t) ;; or nil
N
Hi all,
I found a solution to fix the echo problem of the emacs python shell:
http://stackoverflow.com/questions/8060609/python-interpreter-in-emacs-repeats-lines
That is, in the Interior Python buffer, do
M-: (setq comint-process-echoes t) ;; or nil
Now, if I enter command directly in the
Hi Eric,
Thanks for showing me the smart way of doing this.
cheers,
M
--
mdoy...@ur.rochester.edu (Doyley, Marvin) writes:
> Hi Shiyuan,
>
> I think the problem is that Emacs or babel is using python located in
> /usr/bin or /usr/local/sbin rather than default python or ipython. The way I
> got
> around this is rename python in these locations to python_old and then
Hi Shiyuan,
I think the problem is that Emacs or babel is using python located in
/usr/bin or /usr/local/sbin rather than default python or ipython. The way I
got
around this is rename python in these locations to python_old and then did
a soft link to ipython (i.e., ln -s /anaconda/bin/ipython
Shiyuan writes:
> The two setting doesn't seem to have effect.
> (setq python-shell-interpreter "ipython")
> (setq python-shell-interpreter-args "--pylab")
>
> When I did `C-c C-c` on the SRC block to execute the code, emacs
> created a buffer with the interior python process. When I switched t
The two setting doesn't seem to have effect.
(setq python-shell-interpreter "ipython")
(setq python-shell-interpreter-args "--pylab")
When I did `C-c C-c` on the SRC block to execute the code, emacs created a
buffer with the interior python process. When I switched to the process, I
saw it is pytho
Works for me, see example below
#+BEGIN_SRC python :results output :session foo
x=100
print "hello"
2
print "bye"
#+END_SRC
#+RESULTS:
:
: >>> hello
: 2
: bye
#+BEGIN_SRC python :results output :session foo
print "hello good bye"
print "Printing value from previous session", x
#+END_SRC
#+RES
13 matches
Mail list logo
