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:10:40 +0000 (UTC) [thread overview]
Message-ID: <5a92575-6941-50d-81e6-e96948bdef5@SDF.ORG> (raw)
In-Reply-To: <83tu6hmgn6.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
On Fri, 12 Aug 2022, Eli Zaretskii wrote:
>>
>> Expected result has one window with one line of text in two columns.
>
> Which part of the 2C mode documentation led you to expect to see just
> one window after "F2 1"?
>
The documentation says the following.
```
When you have edited both buffers as you wish, merge them with ‘<F2>
1’ or ‘C-x 6 1’ (‘2C-merge’). This copies the text from the right-hand
buffer as a second column in the other buffer. To go back to two-column
editing, use ‘<F2> s’.
```
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.
--
vl
ALPINE 2.24 GNU Emacs 27.2 NetBSD 9.3
next prev parent reply other threads:[~2022-08-12 19:10 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 [this message]
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
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=5a92575-6941-50d-81e6-e96948bdef5@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 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.