From: Po Lu <luangruo@yahoo.com>
To: help-gnu-emacs@gnu.org
Cc: uzibalqa <uzibalqa@proton.me>
Subject: Re: List of monitor names
Date: Fri, 16 Sep 2022 09:30:32 +0800 [thread overview]
Message-ID: <87v8pow1fr.fsf@yahoo.com> (raw)
In-Reply-To: <lzpmfwpnxe.fsf@3c22fb11fdab.ant.amazon.com> (Sam Steingold's message of "Thu, 15 Sep 2022 13:06:37 -0400")
Sam Steingold <sds@gnu.org> writes:
> For me the solution was based on https://askubuntu.com/q/702071/80483
> and https://askubuntu.com/q/702002/80483; basically you run `xrandr` and
> parse its output.
Well, look no further than display-monitor-attributes-list, which uses
RandR to obtain the same information, but without needing an external
program.
(Unless, of course, your X server only supports Xinerama, in which case
it falls back to that.)
next prev parent reply other threads:[~2022-09-16 1:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 2:55 List of monitor names uzibalqa
2022-09-15 5:04 ` Po Lu
2022-09-15 10:52 ` uzibalqa
2022-09-15 17:06 ` Sam Steingold
2022-09-16 1:30 ` Po Lu [this message]
2022-09-16 1:48 ` uzibalqa
2022-09-16 2:08 ` uzibalqa
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=87v8pow1fr.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=help-gnu-emacs@gnu.org \
--cc=uzibalqa@proton.me \
/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.
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).