From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Van Ly <van.ly@sdf.org>, Eli Zaretskii <eliz@gnu.org>,
57161@debbugs.gnu.org
Subject: bug#57161: 28.1.91; two column windows merge leaves 2nd column window showing
Date: Sat, 13 Aug 2022 14:47:42 +0200 [thread overview]
Message-ID: <CADwFkm=yXaGgbmNewoMwSvzvBeEiHvEGQs1L-VuYKuQAUYAAtQ@mail.gmail.com> (raw)
In-Reply-To: <87mtc8ib7m.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> I've never used this mode before, and I'm kinda flabbergasted that
> something as esoteric as this is bound to <f2> by default.
Esoteric is understating the case, but yes that keybinding should be
freed up (if nothing else, to avoid users accidentally activating
2C-mode).
> Anyway, I don't really see how the current <f2> 1 action makes much
> sense -- it merges the two buffers, but then keeps displaying the
> rightmost window, but extremely narrowly? I'm not sure why that's
> useful.
It gets even worse: when you repeat <f2> 2 <f2> 1 <f2> 2, etc., you
start accumulating windows to the right.
next prev parent reply other threads:[~2022-08-13 12:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 17:55 bug#57161: 28.1.91; two column windows merge leaves 2nd column window showing Van Ly
2022-08-12 19:00 ` Eli Zaretskii
2022-08-12 19:10 ` Van Ly
2022-08-12 19:23 ` Eli Zaretskii
2022-08-12 19:43 ` Van Ly
2022-08-12 19:45 ` Eli Zaretskii
2022-08-13 12:23 ` Lars Ingebrigtsen
2022-08-13 12:47 ` Stefan Kangas [this message]
2022-08-13 14:21 ` Eli Zaretskii
2022-08-14 13:11 ` Van Ly
2022-08-15 5:58 ` Lars Ingebrigtsen
2022-08-15 11:36 ` Eli Zaretskii
2022-08-13 14:15 ` Eli Zaretskii
2022-08-15 5:56 ` Lars Ingebrigtsen
2022-08-16 1:24 ` Michael Heerdegen
2022-08-16 11:11 ` Eli Zaretskii
2022-08-16 22:07 ` Michael Heerdegen
2022-08-17 0:35 ` Van Ly
2022-08-17 11:04 ` Lars Ingebrigtsen
2022-08-14 13:04 ` Van Ly
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkm=yXaGgbmNewoMwSvzvBeEiHvEGQs1L-VuYKuQAUYAAtQ@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=57161@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.