Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>For what it's worth, I do not see the behavior you are seeing in issue #1, "Each buffer visiting a python file gets its own inferior interactive python shell."</p> <p>This is what I did using python.el from Emacs 22.2.</p> <p>C-x C-f foo.py [insert: print "foo"]</p> <p>C-x C-f bar.py [insert: print "bar"]</p> <p>C-c C-z [*Python* buffer appears]</p> <p>C-x o</p> <p>C-c C-l RET ["bar" is printed in *Python*]</p> <p>C-x b foo.py RET</p> <p>C-c C-l RET ["foo" is printed in the same *Python* buffer]</p> <p>Therefore the two files are sharing the same inferior python shell. Perhaps there is some unforeseen interaction between your personal customizations of python-mode and the default behaviors of python.el. Have you tried using python.el without your .emacs customizations and checking if it behaves the same way?</p> <p>The major feature addition of python.el over python-mode is the symbol completion function python-complete-symbol. You can add something like this</p> <pre><code>(define-key inferior-python-mode-map "\C-c\t" 'python-complete-symbol) </code></pre> <p>Then typing</p> <pre><code>&gt;&gt;&gt; import os &gt;&gt;&gt; os.f[C-c TAB] </code></pre> <p>you'll get a *Completions* buffer containing</p> <pre><code>Click &lt;mouse-2&gt; on a completion to select it. In this buffer, type RET to select the completion near point. Possible completions are: os.fchdir os.fdatasync os.fdopen os.fork os.forkpty os.fpathconf os.fstat os.fstatvfs os.fsync os.ftruncate </code></pre> <p>It'll work in .py file buffers too.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload