From: Lars Ingebrigtsen <larsi@gnus.org>
To: 27357@debbugs.gnu.org
Subject: bug#27357: 26.0.50; Emacs starts fullscreen in Ubuntu 17.04
Date: Sun, 16 Jul 2017 18:11:41 +0200 [thread overview]
Message-ID: <877ez8tl8i.fsf@mouse> (raw)
In-Reply-To: <87d190tnrr.fsf@mouse> (Lars Ingebrigtsen's message of "Sun, 16 Jul 2017 17:16:56 +0200")
[-- Attachment #1: Type: text/plain, Size: 72 bytes --]
What I said about the screenshots wasn't totally accurate.
Here's -Q:
[-- Attachment #2: emacs-q.png --]
[-- Type: image/png, Size: 60972 bytes --]
[-- Attachment #3: Type: text/plain, Size: 22 bytes --]
Here's GDK_SCALE=1:
[-- Attachment #4: emacs-q-1.png --]
[-- Type: image/png, Size: 49658 bytes --]
[-- Attachment #5: Type: text/plain, Size: 63 bytes --]
As you can see, the toolbar icons are smaller.
GDK_SCALE=2:
[-- Attachment #6: emacs-q-2.png --]
[-- Type: image/png, Size: 68710 bytes --]
[-- Attachment #7: Type: text/plain, Size: 388 bytes --]
It's identical to just "-Q", which is to be expected, since the default
scale is 2. Except that the menu texts are twice as large, which is not
expected.
So the menu bar font thing is somehow relying on the environment
variable, even if there are no checks for it any more? Urr.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2017-07-16 16:11 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
2017-07-16 16:11 ` Lars Ingebrigtsen [this message]
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=877ez8tl8i.fsf@mouse \
--to=larsi@gnus.org \
--cc=27357@debbugs.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 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).