From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: ynyaaa@gmail.com, 48202@debbugs.gnu.org
Subject: bug#48202: 27.2; wrong frame position
Date: Tue, 04 May 2021 15:06:23 +0300 [thread overview]
Message-ID: <83a6pa66v4.fsf@gnu.org> (raw)
In-Reply-To: <f3827a40-0735-e330-f1d4-a2e2474a6ff9@gmx.at> (message from martin rudalics on Tue, 4 May 2021 10:08:09 +0200)
tags 48202 notabug
close 48202
thanks
> From: martin rudalics <rudalics@gmx.at>
> Date: Tue, 4 May 2021 10:08:09 +0200
>
> I suppose it's those invisible borders which leave an 8 or so pixels
> wide gap. It's highly annoying, especially when you want to display two
> frames side-by-side and yet another reason not to use Windows 10.
Indeed. It turns out this is a Windows 10 "feature": the border of
the window used for resizing by mouse is by default invisible (it can
be made visible by changing your desktop theme). The border is
invisible, but it still takes its space on screen, to allow mouse
resizing. The details can be found here:
https://stackoverflow.com/questions/60700133/windows-desktop-coordinate-system-is-off-for-certain-windows?fireglass_rsn=true
> IIRC the Autohotkey people had some sort of fix for it but maybe I
> misremember.
I don't think there should be a fix: this is how the platform behaves,
and intentionally so.
So I don't think this is a bug, and I'm closing this bug report.
> GNOME shell has a similar problem BTW.
Of course, they all copycat each other.
next prev parent reply other threads:[~2021-05-04 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 17:58 bug#48202: 27.2; wrong frame position ynyaaa
2021-05-03 18:14 ` Eli Zaretskii
2021-05-04 8:08 ` martin rudalics
2021-05-04 12:06 ` Eli Zaretskii [this message]
2021-05-05 7:26 ` 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=83a6pa66v4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48202@debbugs.gnu.org \
--cc=rudalics@gmx.at \
--cc=ynyaaa@gmail.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 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).