From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#18136: 24.4.50; crash in redisplay when calling load-theme Date: Tue, 29 Jul 2014 17:41:56 +0200 Message-ID: <53D7C0C4.7070406@gmx.at> References: <87d2cpxaq1.fsf@holos.localdomain> <8338dkh6wo.fsf@gnu.org> <53D77B06.8040907@gmx.at> <83tx60fjnh.fsf@gnu.org> <53D7A965.30700@gmx.at> <83mwbste5o.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1406648612 4576 80.91.229.3 (29 Jul 2014 15:43:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 29 Jul 2014 15:43:32 +0000 (UTC) Cc: mvoteiza@udel.edu, 18136@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Jul 29 17:43:24 2014 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XC9Yi-00021w-08 for geb-bug-gnu-emacs@m.gmane.org; Tue, 29 Jul 2014 17:43:24 +0200 Original-Received: from localhost ([::1]:46680 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XC9Yh-0001n1-L0 for geb-bug-gnu-emacs@m.gmane.org; Tue, 29 Jul 2014 11:43:23 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53270) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XC9YV-0001bm-4m for bug-gnu-emacs@gnu.org; Tue, 29 Jul 2014 11:43:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XC9YM-0004Le-NU for bug-gnu-emacs@gnu.org; Tue, 29 Jul 2014 11:43:11 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:46951) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XC9YM-0004La-KV for bug-gnu-emacs@gnu.org; Tue, 29 Jul 2014 11:43:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1XC9YL-0004NP-Rz for bug-gnu-emacs@gnu.org; Tue, 29 Jul 2014 11:43:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 29 Jul 2014 15:43:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 18136 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 18136-submit@debbugs.gnu.org id=B18136.140664854116756 (code B ref 18136); Tue, 29 Jul 2014 15:43:01 +0000 Original-Received: (at 18136) by debbugs.gnu.org; 29 Jul 2014 15:42:21 +0000 Original-Received: from localhost ([127.0.0.1]:42217 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1XC9Xc-0004M6-1c for submit@debbugs.gnu.org; Tue, 29 Jul 2014 11:42:20 -0400 Original-Received: from mout.gmx.net ([212.227.17.21]:60645) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1XC9XV-0004Lm-65 for 18136@debbugs.gnu.org; Tue, 29 Jul 2014 11:42:14 -0400 Original-Received: from [62.46.213.117] ([62.46.213.117]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MKt5A-1XC9XO2bIW-0001PY; Tue, 29 Jul 2014 17:42:02 +0200 In-Reply-To: <83mwbste5o.fsf@gnu.org> X-Provags-ID: V03:K0:qirJCoFT4leeJozGtQf6mm1NxMdW2o/vmYNeQE7sZVQRas/++Nu Lef/F/k/UJj4EmG+IaoKd8+Ytm/39mJlDg+8+WFf3mI/uCTLvDCY2HoLFzurygQAGSQx9q+ iprZwMvZh3Se+dT0Oa6vXnQcQuEid3h33a6EBZkJiAMbO8xymXl04PYbgu9Vo2ctWWQj41p SsGKZ+dA7d4+zIaJfYMFA== X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:91946 Archived-At: > I don't have strong feelings about it, and will probably adapt if we > stay with this semantics. But it feels strange, as on a TTY the menu > bar is a line just like any other line, and when the menu bar is not > displayed, I'd expect that line to be used for text. The one use case I can think of is the following: Someone tries to do something special if a specific frame is not as high as needed for displaying some sort of text. In this case it would be nice to have a uniform behavior. But the point is rather moot since the object of reference in this regard is the window and the frame height also counts in the minibuffer and a modeline. So I have no strong feelings about this either. Note that this was an attempt to make the various toolkits behave more similar. But so far I failed in a number of aspects. For example, I was not able to keep the frame height constant when adding/removing the menubar in fullheight mode on a number of GUI builds. > E.g., with your suggested semantics, what would you expect from this: > > emacs -Q > M-: (frame-height) RET > M-x menu-bar-mode RET > M-: (frame-height) RET > > Would you expect to see the 2 results of frame-height identical or > different? Ideally different in fullscreen/maximized/fullheight mode or with `frame-inhibit-implied-resize' non-nil, identical otherwise. > Again, FrameRows and FrameCols updates are triggered in 3 possible > ways: > > . when the terminal is created > > . when we get SIGWINCH > > . when we call change_frame_size > > The last one was missing, which caused bug #17875, whereby switching > to a different frame on the same terminal failed to update FrameRows > and FrameCols, because neither of the first 2 triggers happened. My bad. For some reason I thought these were set in change_frame_size. Is calling change_frame_size necessary when switching frames? What a strange thing to do. martin