unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Van Ly <van.ly@sdf.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 57161@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>, larsi@gnus.org
Subject: bug#57161: 28.1.91; two column windows merge leaves 2nd column window showing
Date: Wed, 17 Aug 2022 00:35:19 +0000 (UTC)	[thread overview]
Message-ID: <33c46633-1c3e-645a-bafd-98eae234cd9b@SDF.ORG> (raw)
In-Reply-To: <87o7wj4zbi.fsf@web.de>

On Wed, 17 Aug 2022, Michael Heerdegen wrote:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>           "I don't use this and I don't like how it works" 
>

I want to use this and I haven't figured out how it works.

My knowledge transfer from "buffer narrow" and "buffer widen" function
doesn't translate to "F2  2" and "F2  1". Doing it wrong means  I keep
creating those secondary column windows I can hide with C-x 1.





  reply	other threads:[~2022-08-17  0:35 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
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 [this message]
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=33c46633-1c3e-645a-bafd-98eae234cd9b@SDF.ORG \
    --to=van.ly@sdf.org \
    --cc=57161@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=michael_heerdegen@web.de \
    /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).