From: Benjamin Slade <beoram@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>, Guix-devel <guix-devel@gnu.org>
Subject: Re: Guix Emacs: use XRandr rather than Gdk?
Date: Wed, 13 Feb 2019 20:09:06 -0700 [thread overview]
Message-ID: <87h8d79ict.fsf@jnanam.net> (raw)
In-Reply-To: <87ftstjbni.fsf@elephly.net>
Hi Ricardo & Guix-devel,
On 2019-02-12T07:59:13-0700, Ricardo Wurmus <rekado@elephly.net> wrote:
> This is done by x-display-monitor-attributes-list, which is defined
> in src/xfns.c. It uses Gdk when Emacs is configured to USE_GTK (the
> code that sets the source to “Gdk” is in an #ifdef).
> We build Emacs with GTK+, but … we may not need to do this as Emacs
> is not a regular GTK client. I recall that there are other oddities
> when using GTK, such as crashes when disconnecting from a remote
> Emacs daemon, which only happens with a GTK build of Emacs.
Looking into this, I suspect the issue is not building the GTK version
(though it would be nice to have a Lucid-toolkit/x11 build available
through Guix at some point as I think I prefer it to the GTK one), but
rather instead that (looking at `emacs.scm`) it seems that Guix isn't
building Emacs with `libxrandr` as one of the (optional) (build time?)
dependencies, and so `frames.el` falls back to using Gdk rather than
XRandr.
What do you think? I can try testing out this theory (i.e. that
including `libxrandr` in `emacs.scm` may be enough to remedy the issue)
at some point, but it may be another week or two before I'll have time
so to do.
-Ben
--
Benjamin Slade - https://babbagefiles.xyz - https://slade.jnanam.net
`(pgp_fp: ,(21BA 2AE1 28F6 DF36 110A 0E9C A320 BBE8 2B52 EE19))
'(sent by mu4e on Emacs running under GNU/Linux . https://gnu.org )
`(Choose Linux ,(Choose Freedom) . https://linux.com )
next prev parent reply other threads:[~2019-02-14 3:09 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
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 [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8d79ict.fsf@jnanam.net \
--to=beoram@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.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/guix.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).