GNU bug report logs - #31745
default-frame-alist sizing parameters set in ~/.emacs are not applied correctly

Previous Next

Package: emacs;

Reported by: "������" <mark.liu.li.ming <at> foxmail.com>

Date: Thu, 7 Jun 2018 07:50:01 UTC

Severity: normal

Tags: moreinfo

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: martin rudalics <rudalics <at> gmx.at>
To: Robert Pluim <rpluim <at> gmail.com>
Cc: 31745 <at> debbugs.gnu.org, 刘力铭 <mark.liu.li.ming <at> foxmail.com>
Subject: bug#31745: 回复: bug#31745: 回复:回复:Re: 回复:bug#31745: Frame's bug whenwindow-system
Date: Thu, 28 Jun 2018 10:02:52 +0200
> Yes, plus parts of emacs obviously believe the frame-parameters, since
> the minibuffer and modeline are not visible.
>
>> What did you use to produce this and does it only happen with scaling?
>> I still do not understand the nature of this bug in the first place.
>
> src/emacs -q --no-site-file --no-site-lisp --no-splash --eval '(setq
> x-wait-for-event-timeout nil)' -l ../emacs-real-26/31745.el
>
> (although it happens with non-nil x-wait-for-event-timeout as well)
> where 31745.el is based off the original reporter's .emacs (attached).

Hmmm...  Does the behavior reproduce just with

emacs -Q --eval "(setq default-frame-alist '((left . 0) (top . 0) (width . 130) (height . 56)))"

56 lines is by default too large for my screen so I can't see the
modeline either.  But I suppose that's not what you both mean.

Also, when you evaluate

(setq default-frame-alist '((left . 0) (top . 0) (width . 130) (height . 56)))

in such a miscreated frame does it turn to the expected state?

BTW we still don't have any valid toolkit/window manager details for
this report yet.  Could you please provide some?

martin




This bug report was last modified 3 years and 53 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.