unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Colin S. Miller" <no-spam-thank-you@csmiller.demon.co.uk>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs as a C Programming IDE Configuration?
Date: Wed, 27 Apr 2011 19:26:32 +0100	[thread overview]
Message-ID: <4db85fa3$0$308$14726298@news.sunsite.dk> (raw)
In-Reply-To: <430fcda1-6ad7-4078-baf8-58608a30c302@glegroupsg2000goo.googlegroups.com>

On 27/04/11 07:47, haziz wrote:
> I also want separate buffers to allow shell commands and to M-x compile.
 > I want it to open into this multi-buffer form automatically when visiting a C source file,
 > rather than having to launch each buffer separately.


Haziz,

I think you are getting confused between a 'buffer', a 'window' and a 'frame'.

In Emacs,
When a file is opened it is read into a buffer; there is normally a one-to-one mapping between
the file and the buffer. (make-indirect-buffer does violate this; but is not relevant here).
A buffer can also have no file associated with it, such as *scratch*, *compilation* etc.

A 'window' is what most other editors call a (non-tiling) MDI child window.
A 'frame' is what most other editors call a top-level window.

Each window displays the contents of one buffer;
M-x displayer-buffer   or M-x 4 C-o  will buffer the current window is currently displaying.

Each frame displays one or more windows,
C-x 2 or C-x 3 will half the size of the current window, and create a new window
to take the remaining space. Both the current and new windows will display the current buffer.


I hope that is a bit clearer,
Colin S. Miller

-- 
Replace the obvious in my email address with the first three letters of the hostname to reply.


  parent reply	other threads:[~2011-04-27 18:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27  6:47 Emacs as a C Programming IDE Configuration? haziz
2011-04-27  9:11 ` Jorgen Grahn
2011-04-27 16:04   ` despen
2011-04-28  6:26     ` Jorgen Grahn
2011-05-09  1:38     ` David Combs
2011-05-09  1:42       ` Pascal J. Bourguignon
2011-05-09 16:30         ` Ted Zlatanov
2011-05-09 16:52           ` Pascal J. Bourguignon
2011-05-21 23:27           ` David Combs
2011-05-22  0:17             ` Pascal J. Bourguignon
2011-05-22 18:47             ` Stefan Monnier
2011-05-22 19:35               ` Jorgen Grahn
2011-05-23 14:50             ` Ted Zlatanov
2011-05-09  3:33       ` despen
2011-05-09 12:53         ` Jorgen Grahn
2011-05-26 14:56     ` Richard Riley
2011-05-26 14:54   ` Richard Riley
2011-04-27 18:26 ` Colin S. Miller [this message]
2011-04-30  0:07   ` haziz
2011-04-29 12:21 ` hjuvi
2011-05-02  3:24   ` rusi
2011-05-02  8:44     ` hjuvi
2011-05-02  9:29       ` Re : " hjuvi
2011-05-26 13:50 ` Richard Riley

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='4db85fa3$0$308$14726298@news.sunsite.dk' \
    --to=no-spam-thank-you@csmiller.demon.co.uk \
    --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).