From: "Ludovic Courtès" <ludo@gnu.org>
To: Benjamin Slade <beoram@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Guix Emacs: use XRandr rather than Gdk?
Date: Tue, 12 Feb 2019 15:20:27 +0100 [thread overview]
Message-ID: <87d0nxks0k.fsf@gnu.org> (raw)
In-Reply-To: <87va1rxalq.fsf@jnanam.net> (Benjamin Slade's message of "Sun, 10 Feb 2019 20:33:37 -0700")
Hi Benjamin,
Benjamin Slade <beoram@gmail.com> skribis:
> In both flown-blown GuixSD as well as Guix on a foreign distro, Guix's
> Emacs seems to use "Gdk" rather than "XRandr" to get screen/monitor
> information. Every other packaged version of Emacs I've tried uses
> "XRandr" to get screen/monitor information. This is an issue because
> "Gdk" apparently doesn't know about individual screens/monitors, but
> only about the aggregate area, whereas "XRandr" returns individual
> screen names (e.g. "DVI-1") and their respective areas. This means that,
> on multi-monitor, where Emacs packages use the `frame.el` library, there
> is no way of distinguishing screens/monitors (problematically for
> packages which try to make reference to different screens,
> e.g. https://gitlab.com/emacsomancer/equake ). I thought I'd start here,
> since I've only found this behaviour on Guix, and `frame.el` doesn't
> seem to be very forthcoming about how it decides whether to use 'Gdk' or 'XRandr'.
Do you know what it would take to fix it? I suppose most Emacs users
would prefer the “correct” behavior. :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-02-12 14:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 3:33 Guix Emacs: use XRandr rather than Gdk? Benjamin Slade
2019-02-12 14:20 ` Ludovic Courtès [this message]
2019-02-12 14:59 ` Ricardo Wurmus
2019-02-12 15:22 ` Pierre Neidhardt
2019-02-12 16:19 ` Benjamin Slade
2019-02-14 3:09 ` Benjamin Slade
2019-02-14 14:35 ` Pierre Neidhardt
2019-02-18 4:54 ` Benjamin Slade
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=87d0nxks0k.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=beoram@gmail.com \
--cc=guix-devel@gnu.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/guix.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.