unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: switching frame focus
Date: Thu, 04 May 2006 12:12:32 -0600	[thread overview]
Message-ID: <e3dgaq$b60$1@sea.gmane.org> (raw)
In-Reply-To: <7f270cb80605040725o7dd996dbnd6abaa66fedb9d62@mail.gmail.com>

John Conrad wrote:
> It always annoyed me that C-x C-b (and lots of other commands) open
> new windows, possibly messing up my window configuration, and almost
> always requiring me to take the extra step of hitting C-x o (or F7,
> which I've bound to 'other-window). About a year ago I took the step
> of adding the following sexp to my .emacs file, which causes all these
> buffer-creating commands to open in the current window:
> 
> (setq same-window-regexps (list ".*"))
> 
> I would be curious to hear from anybody who might share my frustration
> and has found an alternative solution.

I do not share your frustration, but you might try frobbing this 
variable instead:

,----[ C-h v pop-up-windows RET ]
| pop-up-windows is a variable defined in `C source code'.
| Its value is t
|
| Documentation:
| *Non-nil means display-buffer should make new windows.
|
| You can customize this variable.
|
| [back]
`----

I prefer to leave pop-up-windows as its default (t), but:

(global-set-key "\C-x\C-b" 'electric-buffer-list)

and:

(setq special-display-buffer-names
       (nconc '("*Async Shell Command*" "*Backtrace*" "*VC-log*"
                "*compilation*" "*grep*")
	     special-display-buffer-names))
(setq special-display-frame-alist
       (cons '(tool-bar-lines . 0) special-display-frame-alist))

-- 
Kevin

  reply	other threads:[~2006-05-04 18:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04 13:50 switching frame focus Ryan Krauss
2006-05-04 13:56 ` Roger Mason
2006-05-04 14:02   ` Ryan Krauss
2006-05-04 14:12     ` Lennart Borgman
2006-05-04 14:25   ` John Conrad
2006-05-04 18:12     ` Kevin Rodgers [this message]
2006-05-04 14:31 ` Peter Dyballa
2006-05-04 18:16 ` Kevin Rodgers

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='e3dgaq$b60$1@sea.gmane.org' \
    --to=ihs_4664@yahoo.com \
    /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).