From: sbaugh@catern.com
To: Po Lu <luangruo@yahoo.com>
Cc: Spencer Baugh <sbaugh@janestreet.com>, 62164@debbugs.gnu.org
Subject: bug#62164: 29.0.60; ediff behaves poorly by default on tiling window managers
Date: Sun, 02 Apr 2023 11:33:55 +0000 (UTC) [thread overview]
Message-ID: <87v8iemsbh.fsf@catern.com> (raw)
In-Reply-To: <871ql2su9q.fsf@yahoo.com> (Po Lu's message of "Sun, 02 Apr 2023 13:55:13 +0800")
Po Lu <luangruo@yahoo.com> writes:
> I think it is fine to make it a user option, but not the default. BTW,
> it is generally The Right Thing to bind `x-fast-protocol-requests' to t
> around functions which make X requests when those functions are not
> being debugged.
Okay, is there any other patch in this direction which you think would
be an acceptable default?
I think you may not realize how universal the (setq
ediff-window-setup-function 'ediff-setup-windows-plain) configuration
is, all because multi-frame ediff behaves poorly on certain window
managers, I've seen it in many different configuration sources. My
motivation is to make that line of configuration no longer necessary, by
making things work better, if not absolutely right, by default. Just
replacing it with another bit of configuration is much less satisfying.
next prev parent reply other threads:[~2023-04-02 11:33 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 [this message]
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
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=87v8iemsbh.fsf@catern.com \
--to=sbaugh@catern.com \
--cc=62164@debbugs.gnu.org \
--cc=luangruo@yahoo.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).