bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#21415: 25.0.50; Emacs Trunk -- pixelwise width/height for x-create-f


From: Keith David Bershatsky
Subject: bug#21415: 25.0.50; Emacs Trunk -- pixelwise width/height for x-create-frame
Date: Tue, 08 Sep 2015 09:13:04 -0700

Yes, `(setq ns-auto-hide-menu-bar t)` is directly/indirectly related to the new 
large frame appearing one-half out of sight (above the top of the display).  
Setting that variable to the default value of `nil` avoids the problem.  The 
behavior is not caused by the patch, but is something that I recently noticed 
(again) when trying to control the exact parameters upon frame creation.  I 
have been programmatically using `set-frame-position FRAME 0 0` following the 
creation of new frames to compensate for the inability to set the `top` 
correctly on frame creation.

With this feature request (#21415), I was hoping to incorporate the magic of 
`set-frame-size` with the pixelwise argument.  That function is magical because 
it lets a user precisely control the outer dimensions of a frame on OSX -- 
i.e., a user can make the outer dimensions exactly one or more pixels larger or 
smaller.

The patch, from what I understand, seeks to convert pixel specifications into 
the standard character width and standard text line height.  I believe that 
method cannot be used to precisely control the pixel outer dimensions of the 
frame.

The feature request (as I understand it) seeks to control the exact pixel 
height/width of the outer frame -- irregardless of the character width and text 
line height.  For example, the laptop that I am using today uses the following: 
 `(set-frame-size FRAME 1260 774 t)` to precisely fill the display.  The 
corresponding frame parameters are (width . 114) (height . 38); however, those 
are insufficient to fill the screen precisely.  I can get close (but no cigar) 
with (width . 114) (height . 38), and then I need to use `(set-frame-size FRAME 
1260 774 t)` to fix what `make-frame` cannot accomplish.

Keith





reply via email to

[Prev in Thread] Current Thread [Next in Thread]