From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: tomasralph2000@gmail.com
Cc: 63384@debbugs.gnu.org
Subject: bug#63384: x-display-mm-width and x-display-mm-height both
Date: Mon, 05 Jun 2023 17:12:19 +0800 [thread overview]
Message-ID: <873536l1cc.fsf@yahoo.com> (raw)
In-Reply-To: <f488f93b5e298860c99376e4c690ca42@gmail.com> (tomasralph's message of "Sun, 14 May 2023 18:57:28 +0000")
tomasralph2000@gmail.com writes:
> Sigh... The number of excuses GNOME people can come up for their own failings is astonishing. Thomas, if you run: $ wayland-info then, somewhere alongside the descriptions of each output, should be their respective EDID blobs. Would you please send them here, so that I can see if some accurate information can be extracted?
>
> Sure! Here you go:
Hmm, it looks as if my understanding of the Wayland protocol is
incorrect. Upon further investigation, there seems to be no way to
portably obtain the EDID blob from an output.
What does the X modesetting driver think of your output's geometry?
next prev parent reply other threads:[~2023-06-05 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 2:08 bug#63384: x-display-mm-width and x-display-mm-height both return 0 on wayland tomasralph2000
2023-05-10 0:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-13 22:32 ` tomasralph2000
2023-05-14 4:59 ` Eli Zaretskii
2023-05-14 5:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-14 18:57 ` bug#63384: x-display-mm-width and x-display-mm-height both tomasralph2000
2023-06-05 9:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-06-05 3:29 ` bug#63384: x-display-mm-width and x-display-mm-height both return 0 on wayland William A Cadegan-Schlieper
2023-06-05 9:13 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=873536l1cc.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=63384@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=tomasralph2000@gmail.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 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.