From: Phil Sainty <psainty@orcon.net.nz>
To: 62164@debbugs.gnu.org
Subject: bug#62164: 29.0.60; ediff behaves poorly by default on tiling window managers
Date: Wed, 15 Mar 2023 02:13:01 +1300 [thread overview]
Message-ID: <edcf89b1ee2cb076ed079673dabd2f69@webmail.orcon.net.nz> (raw)
In-Reply-To: <ierlek07g9k.fsf@igm-qws-u22796a.mail-host-address-is-not-set>
Spencer Baugh wrote:
> ediff defaults to a multiframe UI on graphical displays. If the
> user is running a tiling window manager on X, the control panel
> frame gets tiled and the whole thing becomes either very ugly or
> unusable.
>
> This is a very long-standing bug, but it should be fixed. Most
> tiling window manager users work around this with:
>
> (setq ediff-window-setup-function 'ediff-setup-windows-plain)
Myself included -- the default value tends to give me a full-screen
control frame entirely obscuring the original frame, which is very
unhelpful indeed.
That problem aside, I've observed that creating a separate GUI
frame can be *significantly* slower; so for me the plain option
is a win for performance as well as usability.
As `ediff-setup-windows-plain' is the faster and the most reliable
option across differing kinds of windowing systems, I am strongly
in favour of changing the default `ediff-window-setup-function'
value to that.
Users who prefer the separate frame can easily make that change in
their configs easily enough, and improvements to better support a
separate control frame can of course still go ahead.
-Phil
prev parent reply other threads:[~2023-03-14 13:13 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
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 [this message]
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=edcf89b1ee2cb076ed079673dabd2f69@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=62164@debbugs.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.