emacs-devel
[Top][All Lists]
Advanced

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

Re: Issue with master build on macOS


From: Angelo Graziosi
Subject: Re: Issue with master build on macOS
Date: Sat, 2 May 2020 23:40:50 +0200 (CEST)

I wonder if this issue is related to this change:

http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=24cb6908d70c14792c686679cb08091447b9c3b1


> Il 2 maggio 2020 alle 23.30 Angelo Graziosi ha scritto:
> 
> 
> It seems that the interfering factor is the desktop file.
> 
> I have renamed it
> 
> mv desktop desktop-save
> 
> Now when I start Emacs without the desktop file it starts right but if I just 
> save it (without having visited any buffer), the bad behavior restarts, 
> shrinking the frame. In this case, one time it starts bad one time it start 
> right... systematically 
> 
> 
> > Il 2 maggio 2020 alle 23.12 Angelo Graziosi ha scritto:
> > 
> > 
> > The build of current master (a941a9e8c22) has a strange behavior.
> > 
> > In the init.el file I have:
> > 
> > (setq default-frame-alist
> >       '(
> >         (width . 115) ; character
> >         (height . 37) ; lines
> >         (left . 325); pixel
> >         (top  .   0); pixel
> >         (font . "Monaco-13") ; font
> >         ))
> > 
> > so that the top-right corner of Emacs frame overlaps the T-R corner of the 
> > screen (it is a 2011 MBP) and its width and height are exactly (leaving 
> > aside scroll bar, tool bar etc.) what is written in the init file.
> > 
> > Now with current build, when I start Emacs its frame, first has the 
> > "natural" (more or less squared) size before the init file is read, then it 
> > is reduce more or less at its half: here its remains for a few second (it 
> > seems to hang); than it takes the final size which is not what the init 
> > file says: about half in width and 70% in height and positioned more or 
> > less at the screen center so that the T-R corners do not overlaps at all.
> > 
> > If close Emacs and the restart it, now it behaves as the init file says. 
> > Good. If I repeat the close-restart operation it fall back to the bad 
> > frame; if I repeat, it results in a good frame and so on. One time it start 
> > bad and another time it start good. I tried this at least 5-6 times.



reply via email to

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