From: martin rudalics <rudalics@gmx.at>
To: Robert Pluim <rpluim@gmail.com>
Cc: Feng Shu <tumashu@163.com>, emacs-devel@gnu.org
Subject: Re: Child-frame can not move to proper position when run "env GDK_SCALE=2 emacs"
Date: Thu, 11 Jan 2018 11:54:34 +0100 [thread overview]
Message-ID: <5A57426A.8040607@gmx.at> (raw)
In-Reply-To: <87vag9j097.fsf@gmail.com>
> That depends on what you mean by 'this'. If you mean 'Emacs always
> works in pixels regardless of scaling', then 'Coordinates and Windows'
> in windows.texi would be a good place. I'm just not sure we can
> guarantee that yet (I know that e.g. frameset-restore misbehaves in
> the presence of scaling, and I haven't tracked down why yet)
I meant when and where programmers have to be aware of the presence of
scaling. If we can make scaling completely transparent, they probably
can ignore this issue. If we can't or there are still unsolved issues
(like the one with the frame size changing when enabling or disabling
scroll bars) we should mention it somewhere.
martin
next prev parent reply other threads:[~2018-01-11 10:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 11:53 Child-frame can not move to proper position when run "env GDK_SCALE=2 emacs" Feng Shu
2018-01-08 18:17 ` martin rudalics
2018-01-08 23:03 ` Feng Shu
2018-01-09 9:43 ` martin rudalics
2018-01-09 10:56 ` Robert Pluim
2018-01-10 10:19 ` martin rudalics
2018-01-10 13:45 ` Robert Pluim
2018-01-11 10:54 ` martin rudalics [this message]
2018-01-09 10:06 ` Robert Pluim
2018-01-10 0:52 ` Dmitry Gutov
2018-01-10 13:19 ` Stefan Monnier
2018-01-10 13:48 ` Robert Pluim
2018-01-10 14:27 ` Dmitry Gutov
2018-01-10 15:08 ` Robert Pluim
2018-01-10 15:36 ` Dmitry Gutov
2018-01-10 15:58 ` Robert Pluim
2018-01-10 16:24 ` Dmitry Gutov
2018-01-10 10:19 ` martin rudalics
2018-01-10 13:35 ` Robert Pluim
2018-01-11 10:54 ` martin rudalics
2018-01-11 0:16 ` Dmitry Gutov
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=5A57426A.8040607@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.com \
--cc=tumashu@163.com \
/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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.