From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: C-x C-f RET change
Date: Thu, 10 Nov 2005 15:35:51 -0800 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICAEJPCOAA.drew.adams@oracle.com> (raw)
In-Reply-To: <85y83wm7r4.fsf@lola.goethe.zz>
> > > I use pop-up-frames = t. Each buffer is in its
own frame, by
> > > default. So, I use `C-x 4 f' to open the same
file in another
> > > frame (cloning the frame, in effect).
> >
> > What's wrong with `C-x 5 2'?
> >
> > Nothing. Good point.
> >
> > I guess I never think of the `C-x 5' prefix, because I use
> > pop-up-frames = t. `C-x 4' generally does the same thing as
> > `C-x 5' in that case, except for a few exceptions like this
> > (there is no `C-x 4 2').
>
> There is C-x 2 though.
>
> I guess I miss your point. Even with pop-up-frames = t,
> `C-x 2' does not open the file in a separate frame (and it
> shouldn't).
Then we probably should have a separate C-x 4 2 for symmetry that
obeys the setting of pop-up-frames.
I don't know about that, but we could. It wouldn't hurt.
It might be somewhat confusing when pop-up-frames = nil. In that case, `C-x
4' would (I imagine) do the same thing as `C-x 2'. (I don't mind.)
`C-x 2' and `C-x 5 2' are not strictly parallel, because window commands
have two prefixes: `C-x' for "this" window and `C-x 4' for "other" window.
Frame commands do not have two prefixes - they have only `C-x 5'.
`C-x 2' says to split _this_ window in two; it doesn't say to do anything
about another window, according to the conventional interpretation. It could
alternatively be thought of, however, as `make-another-window' instead of
`split-window', in which case it would make sense as `C-x 4 2'.
So, it might be worth creating a separate `make-another-window' (or
`make-window-command', in analogy to `make-frame-command'), bound to `C-x 4
2'. With pop-up-frames = nil, this would do the same thing as
`split-window'. With pop-up-frames = t, this would do the same thing as
`make-frame-command'. That would keep the conventions and terminology
consistent.
In any case, `C-x 4 2' is by no means an important requirement.
next prev parent reply other threads:[~2005-11-10 23:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 7:41 C-x C-f RET change Florian Weimer
2005-11-09 9:56 ` Reiner Steib
2005-11-09 10:13 ` Florian Weimer
2005-11-09 13:12 ` Andreas Schwab
2005-11-09 15:29 ` Drew Adams
2005-11-09 16:24 ` David Kastrup
2005-11-10 16:40 ` Drew Adams
2005-11-10 16:56 ` Andreas Schwab
2005-11-10 17:18 ` Drew Adams
2005-11-10 22:34 ` David Kastrup
2005-11-10 22:43 ` Drew Adams
2005-11-10 22:57 ` David Kastrup
2005-11-10 23:35 ` Drew Adams [this message]
2005-11-11 19:38 ` Juri Linkov
2005-11-11 19:47 ` Drew Adams
2005-11-09 19:20 ` Eli Zaretskii
2005-11-09 20:53 ` Edward O'Connor
2005-11-10 2:09 ` Richard M. Stallman
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=DNEMKBNJBGPAOPIJOOICAEJPCOAA.drew.adams@oracle.com \
--to=drew.adams@oracle.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).