unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Thomas Jost via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 54040@debbugs.gnu.org
Subject: bug#54040: 29.0.50; Text becomes blurry on PGTK/Wayland
Date: Fri, 18 Feb 2022 10:03:59 +0100	[thread overview]
Message-ID: <87r180a6m8.fsf@schnouki.net> (raw)
In-Reply-To: <87ley8r4yg.fsf@yahoo.com>

Le 18 février 2022 à 15:47 +08, Po Lu a écrit :
> Thanks, I'll install it then.

I'm afraid I didn't test enough: I just re-built Emacs with your latest
patch, and the issue is still here.

It doesn't happen all the time, though: for instance, it happens in a
frame that takes the whole screen and was never resized, but it doesn't
happen in the frame where I'm writing this message, which was resized to
take half my screen. (I think that was already the case before your
patch, though.)

And once I've resized the frame where it happened, it doesn't happen
anymore, even when it's back to the same size as before.

Could it be related to some difference between the window size requested
by Emacs, and the size assigned by sway?

-- 
Thomas





  reply	other threads:[~2022-02-18  9:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17 10:44 bug#54040: 29.0.50; Text becomes blurry on PGTK/Wayland Thomas Jost via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-18  0:35 ` Morgan Smith
2022-02-18  0:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-18  7:25   ` Thomas Jost via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-18  7:38     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-18  7:44       ` Thomas Jost via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-18  7:47         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-18  9:03           ` Thomas Jost via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-02-18 10:15             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-18 17:07               ` Thomas Jost via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-19  0:59                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-17  0:00 ` Andrew Cohen
2022-03-17  1:04   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-17  1:44     ` Andrew Cohen
2022-03-17  3:45       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-17  4:02         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]           ` <87a6dpb4tm.fsf@ust.hk>
2022-03-17  4:23             ` Po Lu 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

  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=87r180a6m8.fsf@schnouki.net \
    --to=bug-gnu-emacs@gnu.org \
    --cc=54040@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=schnouki@schnouki.net \
    /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).