From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jan D <jan.h.d@swipnet.se>
Cc: 27357@debbugs.gnu.org
Subject: bug#27357: 26.0.50; Emacs starts fullscreen in Ubuntu 17.04
Date: Sun, 16 Jul 2017 17:16:56 +0200 [thread overview]
Message-ID: <87d190tnrr.fsf@mouse> (raw)
In-Reply-To: <87pod0picg.fsf@mouse> (Lars Ingebrigtsen's message of "Sun, 16 Jul 2017 16:27:43 +0200")
Jan, I think you were the one that added the GDK_SCALE thing to Emacs?
I've been chasing down some HiDPI issues:
Lars Ingebrigtsen <larsi@gnus.org> writes:
> That might be a good idea, but I'm not sure where the previous people
> who were working on scaling were going with their work.
>
> Amusingly enough, the
>
> int scale = xg_get_gdk_scale ();
>
> stuff that's sprinkled around just seems to get in the way of fixing
> this stuff. It explicitly looks at the GDK_SCALE environment variable,
> which is (by default) not set. So while some bits of Emacs is using
> that variable to determine some things, querying GTK in the proper way
> (with gtk_widget_get_scale_factor) will get another answer.
Is there a drawback to looking at gtk_widget_get_scale_factor instead of
the GDK_SCALE variable?
Reworking this (on the scratch/hidpi branch) to not look at that
variable seems to fix all my HiDPI issues.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2017-07-16 15:16 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 12:33 bug#27357: 26.0.50; Emacs starts fullscreen in Ubuntu 17.04 Lars Ingebrigtsen
2017-06-14 14:09 ` martin rudalics
2017-06-14 16:38 ` Lars Ingebrigtsen
2017-06-14 17:00 ` Eli Zaretskii
2017-06-14 17:08 ` Lars Ingebrigtsen
2017-06-15 7:59 ` martin rudalics
2017-06-15 9:07 ` Lars Ingebrigtsen
2017-06-15 10:08 ` martin rudalics
2017-06-14 21:50 ` Lars Ingebrigtsen
2017-06-14 22:08 ` Lars Ingebrigtsen
2017-06-15 7:59 ` martin rudalics
2017-06-15 9:11 ` Lars Ingebrigtsen
2017-06-15 9:23 ` Lars Ingebrigtsen
2017-06-15 10:11 ` martin rudalics
2017-07-05 19:42 ` Lars Ingebrigtsen
2017-07-05 20:12 ` Lars Ingebrigtsen
2017-07-06 6:30 ` martin rudalics
2017-07-16 12:40 ` Lars Ingebrigtsen
2017-07-16 12:51 ` martin rudalics
2017-07-16 13:04 ` Lars Ingebrigtsen
2017-07-16 13:29 ` Lars Ingebrigtsen
2017-07-16 13:34 ` Lars Ingebrigtsen
2017-07-16 13:45 ` Lars Ingebrigtsen
2017-07-16 13:55 ` martin rudalics
2017-07-16 13:59 ` Lars Ingebrigtsen
2017-07-16 14:10 ` martin rudalics
2017-07-16 14:27 ` Lars Ingebrigtsen
2017-07-16 15:05 ` Lars Ingebrigtsen
2017-07-16 15:09 ` Lars Ingebrigtsen
2017-07-16 16:39 ` Dmitry Gutov
2017-07-16 16:49 ` Lars Ingebrigtsen
2017-07-17 14:04 ` Robert Pluim
2017-07-17 15:00 ` Lars Ingebrigtsen
2017-07-17 15:16 ` Lars Ingebrigtsen
2017-07-16 15:16 ` Lars Ingebrigtsen [this message]
2017-07-16 16:11 ` Lars Ingebrigtsen
2017-07-17 7:03 ` martin rudalics
2017-07-16 14:19 ` Eli Zaretskii
2017-07-16 14:03 ` Lars Ingebrigtsen
2017-07-16 13:54 ` martin rudalics
2017-06-15 10:09 ` martin rudalics
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=87d190tnrr.fsf@mouse \
--to=larsi@gnus.org \
--cc=27357@debbugs.gnu.org \
--cc=jan.h.d@swipnet.se \
/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/emacs.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).