all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jason Earl <jearl@wegointer.net>
Subject: Re: Preserving window layout
Date: Sat, 07 Jun 2003 21:18:30 -0600	[thread overview]
Message-ID: <871xy5uuih.fsf@smtp.wegointer.net> (raw)
In-Reply-To: mailman.7528.1054997087.21513.help-gnu-emacs@gnu.org

Matthew Calhoun <calhounm@mac.com> writes:

> Hello,
>
> I'm trying to set up Emacs in a way that I think will be nice for
> coding: I have a single full-screen frame with two large side-by-side
> windows for editing source files and whatnot, and below these two
> there's a third window with a shell in it, which takes up the entire
> frame width. It looks something like this:
>
> -----------------------
> |          |          |
> |          |          |
> |  source  |  source  |
> |          |          |
> |          |          |
> -----------------------
> |        shell        |
> -----------------------
>
> Sort of a poor man's IDE. The problem is, when I do something like
> command-apropos it wreaks havoc on my nice little environment - the
> shell buffer grows to take up half of the frame, and the *Apropos*
> buffer has taken the place of *shell*.
>
> What I would like do is keep this basic layout the same, viewing
> various buffers only in the top two windows, and keeping the shell
> window undisturbed at the bottom. So, is there some way to "lock" a
> screen layout, or at least a single window? And can I prevent my shell
> buffer from being replaced by other buffers?
>
> In case it matters, I'm using Emacs 21.1.1 in Mac OS X's Terminal
> application.

I don't know anything about Mac OS X, but I quite often do something
like this:


  +-----------+	 +-----------+ +--+
  |           |	 |           | |  |
  |           |	 |           | |  |
  |  source   |	 |   docs    | |  |   speedbar
  |           |	 |           | |  |   ----
  |           |	 |           | | <+--/ 	  
  |           |	 |           | |  |	 
  |           |	 |           | |  |	 
  +-----------+	 |           | |  |	 
  |           |	 |           | |  |	 
  |           |	 |           | |  |	 
  |  shell    |	 |           | |  |	 
  |           |	 |           | |  |	 
  +-----------+	 +-----------+ +--+

Basically this is two normal frames, one of them with a small shell
window and a speed bar.  It does pretty much everything your setup
does, but it's a bit easier to maintain.  It takes a fair amount of
screen real estate, but so does your setup.

Jason

  parent reply	other threads:[~2003-06-08  3:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.7528.1054997087.21513.help-gnu-emacs@gnu.org>
2003-06-07 15:10 ` Preserving window layout Glyn Millington
2003-06-07 20:32 ` Galen Boyer
2003-06-07 21:16 ` Johan Bockgård
2003-06-11 18:53   ` Preserving window layout (follow up) Matthew Calhoun
2003-06-08  3:18 ` Jason Earl [this message]
2003-06-07 14:41 Preserving window layout Matthew Calhoun

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

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

  git send-email \
    --in-reply-to=871xy5uuih.fsf@smtp.wegointer.net \
    --to=jearl@wegointer.net \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.