[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: List of monitor names
From: |
uzibalqa |
Subject: |
Re: List of monitor names |
Date: |
Fri, 16 Sep 2022 02:08:33 +0000 |
Sent with Proton Mail secure email.
------- Original Message -------
On Friday, September 16th, 2022 at 1:48 AM, uzibalqa <uzibalqa@proton.me> wrote:
> ------- Original Message -------
> On Friday, September 16th, 2022 at 1:30 AM, Po Lu luangruo@yahoo.com wrote:
>
>
>
> > 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.)
>
>
> With "display-monitor-attributes-list" I get
>
> (((geometry 1080 1152 1366 768) (workarea 1080 1152 1311 768) (mm-size 344
> 194)
> (frames #<frame scratch 0x16f3510> #<frame Speedbar 0x2b84190>)
>
> (source . "Gdk")) ((geometry 0 0 1080 1920) (workarea 0 0 1080 1920)
> (mm-size 477 268) (frames) (source . "Gdk")))
>
> But still nobody has told me what frame should I use for the initial frame
> (seems it
> is usually scratch). What input should frame be in the command
> "(frame-outer-width frame)".
Doing (frame-outer-width "*scratch*") gives
Debugger entered--Lisp error: (error "*scratch* is not a live frame")
signal(error ("*scratch* is not a live frame"))
error("%s is not a live frame" "*scratch*")
window-normalize-frame("*scratch*")
frame-outer-width("*scratch*")