[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (set-frame-position ... 0 0) renders a few pixels right of left edge
From: |
David Karr |
Subject: |
Re: (set-frame-position ... 0 0) renders a few pixels right of left edge |
Date: |
Mon, 26 Feb 2024 11:20:17 -0800 |
On Thu, Feb 22, 2024 at 2:07 PM David Karr <davidmichaelkarr@gmail.com>
wrote:
> On Windows 11, using Cygwin Emacs, I have the following at the top of my
> .emacs file:
>
> (set-frame-position (selected-frame) 0 0)
> (set-frame-height (selected-frame) 57)
>
> When the window appears, the left edge is a few pixels to the right of the
> left edge. If I throw the mouse cursor to the edge of the screen, the emacs
> window is not in focus.
>
> Each time emacs starts up, I have to manually drag the window a few pixels
> to the left so it aligns to the left edge.
>
> I thought perhaps that giving the X value a negative value would help, but
> the doc says that would result in a completely different behavior, making
> the right edge relative to the right edge of the screen. I suppose I could
> drill down until I figured out the exact negative value from the right
> edge, but that is a little annoying, and it would break if I connected to a
> larger monitor.
>
I saw in the archives that Eli Zaretskii had replied to this, but I never
saw it in my inbox. I'll try to address what he said.
This is what I saw both before and after moving the window:
Before moving it:
((outer-position 0 . 0) (outer-size 689 . 1007) (external-border-size 8 .
8) (title-bar-size 651 . 23) (menu-bar-external . t) (menu-bar-size 673 .
20) (tab-bar-size 0 . 0) (tool-bar-external) (tool-bar-position . top)
(tool-bar-size 673 . 36) (internal-border-width . 0))
After moving it:
((outer-position -8 . 0) (outer-size 689 . 1007) (external-border-size 8 .
8) (title-bar-size 651 . 23) (menu-bar-external . t) (menu-bar-size 673 .
20) (tab-bar-size 0 . 0) (tool-bar-external) (tool-bar-position . top)
(tool-bar-size 673 . 36) (internal-border-width . 0))
I assume this agrees with what you said, but I don't know how to solve the
problem. I have no idea why my Windows 11 laptop is doing this. Note that
in the last couple of days, I proceeded to set up a new work laptop (HP).
Both the old (also HP) and new laptop behave exactly the same in this
respect.