From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: luangruo@yahoo.com, sbaugh@catern.com, 62164@debbugs.gnu.org
Subject: bug#62164: 29.0.60; ediff behaves poorly by default on tiling window managers
Date: Wed, 28 Jun 2023 14:56:36 +0300 [thread overview]
Message-ID: <83leg3vlzf.fsf@gnu.org> (raw)
In-Reply-To: <ier8rc4z8wq.fsf@janestreet.com> (message from Spencer Baugh on Tue, 27 Jun 2023 21:13:09 -0400)
> From: Spencer Baugh <sbaugh@janestreet.com>
> Cc: luangruo@yahoo.com, sbaugh@catern.com, 62164@debbugs.gnu.org
> Date: Tue, 27 Jun 2023 21:13:09 -0400
>
> * lisp/vc/ediff-wind.el (ediff-x-utility-control-frame): Add
> defcustom. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Copy/pasta, right?
> +(defcustom ediff-x-floating-control-frame nil
A better name is ediff-floating-control-frame.
> + "If non-nil, the control frame will float under most X WMs.
> +
> +The control frame will be give the window type \"utility\". On
> +most tiling window managers, this will cause the control frame to
> +be floating rather than tiled. It should be harmless on other
> +well-behaved window managers."
I would document this slightly differently:
If not-nil, try making the control frame be floating rather than tiled.
If your X window manager makes the Ediff control frame a tiled one,
set this to a non-nil value, and Emacs will try to make it floating.
This only has effect on X displays.
next prev parent reply other threads:[~2023-06-28 11:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 16:44 bug#62164: 29.0.60; ediff behaves poorly by default on tiling window managers Spencer Baugh
2023-03-14 0:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-14 1:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-16 15:07 ` Spencer Baugh
2023-03-17 1:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-02 1:53 ` sbaugh
2023-04-02 5:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-02 11:33 ` sbaugh
2023-05-09 18:27 ` Spencer Baugh
2023-05-09 19:15 ` Eli Zaretskii
2023-06-05 21:56 ` Spencer Baugh
2023-06-05 23:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-06 11:29 ` Eli Zaretskii
2023-06-28 1:13 ` Spencer Baugh
2023-06-28 1:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-28 11:56 ` Eli Zaretskii [this message]
2023-06-28 12:55 ` Spencer Baugh
2023-06-28 13:40 ` Robert Pluim
2023-07-03 19:21 ` sbaugh
2023-07-06 7:51 ` Eli Zaretskii
2023-03-14 3:06 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-14 13:13 ` Phil Sainty
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=83leg3vlzf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62164@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=sbaugh@catern.com \
--cc=sbaugh@janestreet.com \
/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).