emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Memnon Anon <gegendosenfleisch@googlemail.com>
To: emacs-orgmode@gnu.org
Subject: Re: open a source code
Date: Mon, 28 May 2012 17:06:22 +0000 (UTC)	[thread overview]
Message-ID: <87y5ockzvk.fsf@mean.albasani.net> (raw)
In-Reply-To: 87mx4sflto.fsf@cica.cica

Petro <khoroshyy@gmail.com> writes:

> If I open a python code using "C-c '", emacs window splits into two. One
> with with python mode and another with org mode. How can I prevent
> splitting and make python window full screen?

Good question, lets check the docs:

F1 i, d, m "org" TAB RET.

Working with source code, Editing source code ...
Yep, what about this: 

,----[ (info "(org)Editing source code") ]
| `org-src-window-setup'
|      Controls the way Emacs windows are rearranged when the edit buffer
|      is created.
`----

Okay, lets have a look, shall we?

,----[ F1-v "org-src-window-setup" ]
| Documentation:
| How the source code edit buffer should be displayed.
| Possible values for this option are:
| 
| current-window    Show edit buffer in the current window, keeping all other
|                   windows.
| other-window      Use `switch-to-buffer-other-window' to display edit buffer.
| reorganize-frame  Show only two windows on the current frame, the current
|                   window and the edit buffer. When exiting the edit buffer,
|                   return to one window.
| other-frame       Use `switch-to-buffer-other-frame' to display edit buffer.
|                   Also, when exiting the edit buffer, kill that frame.
`----

Default seems to be 'reorganize-frame, which is obviously not what you
want.

current-window would be a good choice if you usually start with one
window in the beginning. Or try other-frame.

Is this helpful? Or is this not what you want?
If you missed it in the docs, where would you have expect it? 
How and where did you look for this info?

hth
Memnon

      parent reply	other threads:[~2012-05-28 17:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-28 13:59 open a source code Petro
2012-05-28 16:36 ` Eric Schulte
2012-05-28 17:06 ` Memnon Anon [this message]

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.orgmode.org/

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

  git send-email \
    --in-reply-to=87y5ockzvk.fsf@mean.albasani.net \
    --to=gegendosenfleisch@googlemail.com \
    --cc=emacs-orgmode@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).