From: Van Ly <van.ly@sdf.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 57161@debbugs.gnu.org
Subject: bug#57161: 28.1.91; two column windows merge leaves 2nd column window showing
Date: Fri, 12 Aug 2022 19:43:01 +0000 (UTC) [thread overview]
Message-ID: <7cf48bf-992e-8c7f-92be-bf88484e812@SDF.ORG> (raw)
In-Reply-To: <83sfm1mfjo.fsf@gnu.org>
On Fri, 12 Aug 2022, Eli Zaretskii wrote:
>
> Where does this say that the other window gets deleted?
>
I expect F2 2, F2 1 will get me back to the frame and window
layout at the moment before F2 2.
>> Documentation and actual behavior drift apart is a common place
>> expectation in software. My familiarity with C-x 1 carried over to
>> C-x 6 1.
>
> In this case, extrapolating from "C-x 1" leads to incorrect
> expectations.
>
> I see no bug in the current behavior of "F2 1".
>
I see.
Before pressing F2 2, a new file called "text.text" is in text mode.
Pressing F2 2, F2 1, leaves the file in Text 2C mode and that 2nd
column window is pushed to the side. Is there a way to get back to
plain text mode and the original one window? M-x normal-mode won't.
M-x text-mode won't. The modeline shows "2C". I don't know what to
do with that marginal window.
next prev parent reply other threads:[~2022-08-12 19:43 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 [this message]
2022-08-12 19:45 ` Eli Zaretskii
2022-08-13 12:23 ` Lars Ingebrigtsen
2022-08-13 12:47 ` Stefan Kangas
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
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=7cf48bf-992e-8c7f-92be-bf88484e812@SDF.ORG \
--to=van.ly@sdf.org \
--cc=57161@debbugs.gnu.org \
--cc=eliz@gnu.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).