From: Lars Bungum <lars.bungum@idi.ntnu.no>
To: help-gnu-emacs@gnu.org
Subject: Python mode: make emacs use existing *Python* frame, and not open a new one
Date: Thu, 05 May 2011 16:44:48 +0200 [thread overview]
Message-ID: <ipud4v$1bv$1@orkan.itea.ntnu.no> (raw)
Hi,
I am using python-mode to write python code in Emacs, and when I use the
useful C-c C-c key combination to interpret the buffer, Emacs always
opens another window inside the window I am using.
I prefer using Emacs split in two windows (one on each physical screen)
where I program in one of them and use the Python interpreter in the
other. Is there a way I can tell Emacs to use the *Python* buffer in
the Window that is already open instead of creating a new one?
--lars
next reply other threads:[~2011-05-05 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 14:44 Lars Bungum [this message]
2011-05-06 17:21 ` Python mode: make emacs use existing *Python* frame, and not open a new one rusi
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='ipud4v$1bv$1@orkan.itea.ntnu.no' \
--to=lars.bungum@idi.ntnu.no \
--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).