all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: van.ly@sdf.org, 57161@debbugs.gnu.org
Subject: bug#57161: 28.1.91; two column windows merge leaves 2nd column window showing
Date: Mon, 15 Aug 2022 07:56:54 +0200	[thread overview]
Message-ID: <87mtc6dp7d.fsf@gnus.org> (raw)
In-Reply-To: <83czd4mdqm.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 13 Aug 2022 17:15:13 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> I can see a certain logic behind what "F2 1" does, and since neither
> of us uses this mode, I don't think our opinions otherwise matter.

We have one known user of this mode, and 100% of that one user says that
what `<f2> 1' does doesn't make much sense, so perhaps we should listen
to that user?






  reply	other threads:[~2022-08-15  5:56 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 [this message]
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=87mtc6dp7d.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=57161@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 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.