From: Lars Ingebrigtsen <larsi@gnus.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 27357@debbugs.gnu.org
Subject: bug#27357: 26.0.50; Emacs starts fullscreen in Ubuntu 17.04
Date: Sun, 16 Jul 2017 17:05:15 +0200 [thread overview]
Message-ID: <87o9sktob8.fsf@mouse> (raw)
In-Reply-To: <87pod0picg.fsf@mouse> (Lars Ingebrigtsen's message of "Sun, 16 Jul 2017 16:27:43 +0200")
[-- Attachment #1: Type: text/plain, Size: 439 bytes --]
Wow.
After getting rid of the GDK_SCALE stuff (well, replacing it by querying
GTK for what scaling it's using), and doing the same with the
positioning as Ryan did (I ended up writing my own version to make it
fit better with the call conventions of the old GDK_SCALE stuff)...
Things just work.
That is, my Emacs opens with the right size window, unmaximized, and
everything is hunky dory. I think.
Let's see...
Here's "emacs -Q":
[-- Attachment #2: emacs-q.png --]
[-- Type: image/png, Size: 60972 bytes --]
[-- Attachment #3: Type: text/plain, Size: 243 bytes --]
That looks totally normal, doesn't it? (I've forgotten how it's
supposed to look like after living with it opening in the wrong size for
some weeks. :-))
It looks identical with "GDK_SCALE=1 emacs -Q".
What about "GDK_SCALE=2 emacs -Q"?
[-- Attachment #4: emacs-q-2.png --]
[-- Type: image/png, Size: 68710 bytes --]
[-- Attachment #5: Type: text/plain, Size: 388 bytes --]
Hm... the only thing that happened was that the menu bar font is twice
as large? Hm... Is that's what's supposed to happen?
If I say set the scale to 4, then the frame is twice as wide, and the
font is even huger.
Hm... I feel like this isn't making total sense... Or is it?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2017-07-16 15:05 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 [this message]
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
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=87o9sktob8.fsf@mouse \
--to=larsi@gnus.org \
--cc=27357@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).