From: Van Ly via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 64868@debbugs.gnu.org
Subject: bug#64868: 29.1; C-x O binding suggestion for (other-window -1)
Date: Wed, 2 Aug 2023 13:07:42 GMT [thread overview]
Message-ID: <202308021307.372D7gOS017787@sdf.org> (raw)
In-Reply-To: <83pm4eokc7.fsf@gnu.org> (message from Eli Zaretskii on Wed, 26 Jul 2023 16:47:52 +0300)
> Date: Wed, 26 Jul 2023 16:47:52 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 64868@debbugs.gnu.org
>
> > Date: Wed, 26 Jul 2023 13:19:48 GMT
> > From: Van Ly <van.ly@sdf.org>
> > Cc: 64868@debbugs.gnu.org
> >
> > > What's wrong with "C-- C-x o" (or "C-u - C-x o" if you are on a
> > > text-mode terminal)?
> >
> > C-- shrinks the font size depending on the console.
>
> In "emacs -Q"? Doesn't happen for me.
>
``emacs -Q'' inside kde/konsole has this and more discomforts for me.
> > To run the universal-argument command I map the C-u to somewhere else
> > as the fingers more frequently use C-u for rubbing out from the
> > current position to left margin position zero. I use Super-u or
> > Escape-u for universal-argument and avoid that if I can because Super
> > and Escape are read differently depending on console and keyboard
> > context.
>
> So you will need to find a binding for (other-window -1) that is
> specific to your customizations. There's no need to change the
> defaults for that, because key bindings are sort of user
> customizations that users are encouraged to do to suit their needs and
> preferences.
>
I found a better mapping than C-x o,
C-x <up> for other-window in the other direction
C-x <down> for other-window
works well with C-x <left>/<right>
A lot of mentions on the Internet say Emacs's drawback is the need to
customize it because the defaults are quirky from a different time
before keyboard commoditification.
> > > We don't have too many free key sequences, so "wasting" one on
> > > something that can be easily achieved via an existing binding is not a
> > > good idea, IMO.
> >
> > I agree. I guess we could use C-x O for now until something more
> > preferable comes along to occupy the big O. org-mode? That fits
> > nicely next to project.
>
> No, I mean we should not give this command a key binding at all, not
> by default. There's no need, since you can easily do it for you
> without changing any default bindings.
>
Repeating several C-u -1 C-x o is suboptimal for me.
>
> Neither do "C-h c C-x p C-h", so the above is the expected behavior,
> unrelated to the fact that you rebind C-h.
>
The pain for the gain from remapping C-h is worth it for me, just need
f1 to function equally in place of C-h for tablike completion.
Is there a way to overlay ``b'' in the read-only modes such as
view-mode to function in the opposite direction to SPC. The
``self-insert'' default for keys in read-only modes feels like a bug
you step on, notice but don't squish by habit.
next prev parent reply other threads:[~2023-08-02 13:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 6:46 bug#64868: 29.1; C-x O binding suggestion for (other-window -1) Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-26 11:15 ` Eli Zaretskii
2023-07-26 13:19 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-26 13:47 ` Eli Zaretskii
2023-08-02 13:07 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-08-02 14:26 ` Drew Adams
2023-08-02 16:25 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-02 16:45 ` Drew Adams
2023-08-03 2:42 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-02 14:28 ` Eli Zaretskii
2023-08-02 16:45 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-02 17:01 ` Eli Zaretskii
2023-07-26 14:37 ` Drew Adams
2023-08-02 21:00 ` Jim Porter
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=202308021307.372D7gOS017787@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=64868@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=van.ly@sdf.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.
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).