From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 11113@debbugs.gnu.org, thomas.luebking@gmail.com,
Tristan Miller <tristan@logological.org>,
Jorge Adriano Branco Aires <jorge.adriano@gmail.com>
Subject: bug#11113: 23.3; Access to the mini-buffer in auctex mode triggers window resize in KDE (Kwin)
Date: Sun, 09 Jun 2024 20:01:09 +0800 [thread overview]
Message-ID: <87y17ecol6.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkm=a0YFqA-VsOJEY22+bhbV8n7NNaSh9Q6-CuwyFjEFQxw@mail.gmail.com> (Stefan Kangas's message of "Sun, 9 Jun 2024 07:43:45 -0400")
Stefan Kangas <stefankangas@gmail.com> writes:
> Does this affect all KDE users?
They're the only judges of that.
> If so, that sounds like a pretty nasty bug. Is there any feasible
> workaround that we could do on our end?
No, but KDE users might easily apply:
(setq frame-resize-pixelwise t)
in their early initialization files.
next prev parent reply other threads:[~2024-06-09 12:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <adf0883b-6f7f-4963-8cd2-150936a0c84a@logological.org>
2012-03-28 15:57 ` bug#11113: 23.3; Access to the mini-buffer in auctex mode triggers window resize in KDE (Kwin) Jorge Adriano Branco Aires
2019-11-01 20:17 ` Stefan Kangas
2019-12-01 7:51 ` Stefan Kangas
2024-06-07 22:19 ` bug#11113: [Tristan Miller] " Stefan Kangas
2024-06-08 13:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-08 13:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-09 11:43 ` Stefan Kangas
2024-06-09 12:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-06-09 12:06 ` Stefan Kangas
2024-06-09 12:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-12 14:35 ` Tristan Miller via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87y17ecol6.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=11113@debbugs.gnu.org \
--cc=jorge.adriano@gmail.com \
--cc=luangruo@yahoo.com \
--cc=stefankangas@gmail.com \
--cc=thomas.luebking@gmail.com \
--cc=tristan@logological.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.