From: "John Conrad" <john.emerson.conrad@gmail.com>
Subject: Re: switching frame focus
Date: Thu, 4 May 2006 10:25:11 -0400 [thread overview]
Message-ID: <7f270cb80605040725o7dd996dbnd6abaa66fedb9d62@mail.gmail.com> (raw)
In-Reply-To: <y65r739sxkp.fsf@minnie.esd.mun.ca>
On 5/4/06, Roger Mason <rmason@esd.mun.ca> wrote:
> "Ryan Krauss" <ryanlists@gmail.com> writes:
>
> > This seems like a silly question, but I have goolged around and not
> > come up with an answer. If I split my window using C-x 2, how do I
> > switch the focus between the two split frames (or whatever emacs calls
> > them). I have an aversion to touching the mouse, but basically I want
> > to click in the other window and work over there and then click
> > back. I also want to use this when I do C-x C-b to list the buffers.
> > I want
> > to switch into the buffer list to choose the one I want to open.
>
> C-x o cycles between frames.
>
> HTH,
>
> Roger
Specifically, the command/function 'other-window' cycles through
windows, and, as Roger pointed out, it is bound by default to the
C-x o.
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.
Regards,
John Emerson Conrad
next prev parent reply other threads:[~2006-05-04 14:25 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 [this message]
2006-05-04 18:12 ` Kevin Rodgers
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=7f270cb80605040725o7dd996dbnd6abaa66fedb9d62@mail.gmail.com \
--to=john.emerson.conrad@gmail.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).