[Top][All Lists]

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

bug#31745: 回复: bug#31745: 回复:回复:Re: 回复:bug#31745: Frame's bug whenwindow

From: martin rudalics
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?


reply via email to

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