From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#34179: 27.0.50; message hangs when buffer with process visible Date: Fri, 25 Jan 2019 11:36:24 +0100 Message-ID: <5C4AE6A8.9030006@gmx.at> References: <87fttj4dgj.fsf@web.de> <83ef938hik.fsf@gnu.org> <874l9yp50z.fsf@web.de> <87y37anpoj.fsf@web.de> <83pnsm6rxs.fsf@gnu.org> <878szanlua.fsf@web.de> <8736pinlk4.fsf@web.de> <87womum615.fsf@web.de> <87r2d2m5jf.fsf@web.de> <5C49E24F.7080800@gmx.at> <87d0olncf4.fsf@web.de> <877eetnba1.fsf@web.de> <83ef917tf7.fsf@gnu.org> <83bm457s49.fsf@gnu.org> <5C4ADA96.4010400@gmx.at> <83y37959hp.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="125140"; mail-complaints-to="usenet@blaine.gmane.org" Cc: michael_heerdegen@web.de, 34179@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Jan 25 11:53:20 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gmz6u-000WL6-BJ for geb-bug-gnu-emacs@m.gmane.org; Fri, 25 Jan 2019 11:53:20 +0100 Original-Received: from localhost ([127.0.0.1]:41996 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gmz6p-0002au-Lc for geb-bug-gnu-emacs@m.gmane.org; Fri, 25 Jan 2019 05:53:15 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:40800) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gmyr9-000652-9T for bug-gnu-emacs@gnu.org; Fri, 25 Jan 2019 05:37:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gmyr8-0003GS-FX for bug-gnu-emacs@gnu.org; Fri, 25 Jan 2019 05:37:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:45298) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gmyr8-0003GE-CM for bug-gnu-emacs@gnu.org; Fri, 25 Jan 2019 05:37:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gmyr7-0001ok-Il for bug-gnu-emacs@gnu.org; Fri, 25 Jan 2019 05:37:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 25 Jan 2019 10:37:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 34179 X-GNU-PR-Package: emacs Original-Received: via spool by 34179-submit@debbugs.gnu.org id=B34179.15484126036963 (code B ref 34179); Fri, 25 Jan 2019 10:37:01 +0000 Original-Received: (at 34179) by debbugs.gnu.org; 25 Jan 2019 10:36:43 +0000 Original-Received: from localhost ([127.0.0.1]:44579 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gmyqp-0001oE-7C for submit@debbugs.gnu.org; Fri, 25 Jan 2019 05:36:43 -0500 Original-Received: from mout.gmx.net ([212.227.17.20]:47497) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gmyqo-0001o2-2r for 34179@debbugs.gnu.org; Fri, 25 Jan 2019 05:36:42 -0500 Original-Received: from [192.168.1.101] ([46.125.249.96]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Lqhaw-1hPuAD1gjC-00eJNZ; Fri, 25 Jan 2019 11:36:35 +0100 In-Reply-To: <83y37959hp.fsf@gnu.org> X-Provags-ID: V03:K1:QWCGieC6/hh/2GSk1AMmfIubn9+DZXfRO44afYHlxqD9GtZMA4m T/Wmz6BfACFs6WZ8nRWtDuwUkiWHKil7r2wog8S197WNUWl0+9QyFmRyiz08sx3Bf0iXhK7 AaYAgOtQYdVj7yKDw6R44TJARDMz+nMyCU89QPkPZ1DhsH6xApX/kRPUo5pyqRW9iAFHqJh bwuq95IaujVUlFEINKGaQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:smspj0QCYjE=:bG2RvKiZFNuq0mobnvTDkP r2nQaGXuBZnKLsKqfXiKRgep1ArIwYFNO/4LiFGPfZnG1JHX3o3VKHvVzVrWl/thXX7UWP5QP 2ij2vv1xoHbgKt/jT3d8umZgIubSABnC0J41Hf7btKKepNrJZztrS2Ycj5VDwibJNv8KLpiM2 Awa6Y5NckFiCRk1gMzYebvM/ra2nOZsTpdfjk04sZrKOqYh3Y2U8WiZhtm4cUABF/Cz0N/FYu N848Te1Vli8sqKS8bdgig6Fjhhc2TKPKNdx28CEGAN0c6YyZ5Byd8M/hTlzU62JCQd7W7fIYt PAmBrAB35BUaKGCi5DOTU67GVSa1qt0bHM4rRGkY4ikNHRs+z2mU6zcptdT35bONTTfBt+asT zsTohgQZVkrlt0QYjGCYDcPxwkF3jwKsPqXdsxBNEm9m64xOZIpMsRuGFikV7gMXxUgFlvvdZ 7p7zOhhj07ENvvx77IXgP/q464ErVaggz3pb1kepaPSjg8dUzUcrhoVSo5dTKu03sutcxj5Y1 m8b37cEWK/b9GeZQLBg66dhLPYTF78+JYNvGKJt36XXbPGSzhtYtfz+LGSin39OJ1wQNhxEa8 Ghwe59GFb7idfrxHrv+EhLwUz3QJI+dQHuuLaZhtCxEbw69eTYa9wzuYgebG6jo+XNptMO8oL ybRr0617FVfLU9Hd5ZBMN1ldaalnsag3MLPPk/wZPLSLPh1WRjD4fPy+p30IY6VRx5zgBix8T 0sKA6yRvtxzMLx4o4K0bD7AXRxtUOTeU0JoI/d2yDngrb05sP03/zi/KH/1oL46Hc28QMAXD X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.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" Xref: news.gmane.org gmane.emacs.bugs:154768 Archived-At: >> If I replace the line >> >> (with-selected-window (window-normalize-window window t) >> >> of 'window-max-chars-per-line' by the line >> >> (with-current-buffer (window-buffer window) >> >> the problem persists. So it is not the 'select-window' call per se >> that causes the trouble. > > That's because both selecting a window and changing its buffer sets > windows_or_buffers_changed via redisplay_other_windows. But =E2=80=98with-current-buffer=E2=80=99 does not change a window's buff= er. Or what am I missing? >> The problem is with having that separate frame that gets its echo >> area resized. > > What separate frame? The one from Michael's scenarios. As in I can provoke the hang in emacs -Q by just doing M-x shell, C-x 5 2, and M-: (message "A\nB"). I can't get the hang with a single frame. Can you? >> Using 'window-size-change-functions' (patch attached) instead of >> 'window-configuration-change-hook' fixes the problem here. > > That might be a good change anyway, but the more general problem of > having an easily triggered infloop in redisplay_internal remains, and > we should fix that, IMO. It's an infloop triggered in =E2=80=98window-configuration-change-hook=E2= =80=99 and it was always easy to trigger an infloop there. Obviously, resizing the minibuffer window did not trigger `window-configuration-change-hook' at all before my change. > Let me turn the table and ask: why do we need to retry redisplay when > some function called from run_window_change_functions does something > that requires redisplay? Why not leave that to the next redisplay > cycle? Bug#34138 is one example why redisplay should be triggered from within a function on 'window-configuration-change-hook'. martin