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 17:51:53 +0100 Message-ID: <5C4B3EA9.5030900@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> <5C4AE6A8.9030006@gmx.at> <83woms6ex9.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="106611"; 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 17:53:15 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 1gn4jD-000Rcy-44 for geb-bug-gnu-emacs@m.gmane.org; Fri, 25 Jan 2019 17:53:15 +0100 Original-Received: from localhost ([127.0.0.1]:47308 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gn4j8-00007a-Vg for geb-bug-gnu-emacs@m.gmane.org; Fri, 25 Jan 2019 11:53:11 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:57218) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gn4j3-00007P-0l for bug-gnu-emacs@gnu.org; Fri, 25 Jan 2019 11:53:05 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gn4j2-0002V7-4F for bug-gnu-emacs@gnu.org; Fri, 25 Jan 2019 11:53:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:46193) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gn4j0-0002UQ-8H for bug-gnu-emacs@gnu.org; Fri, 25 Jan 2019 11:53:04 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gn4j0-0000Kp-45 for bug-gnu-emacs@gnu.org; Fri, 25 Jan 2019 11:53:02 -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 16:53:02 +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.15484351341228 (code B ref 34179); Fri, 25 Jan 2019 16:53:02 +0000 Original-Received: (at 34179) by debbugs.gnu.org; 25 Jan 2019 16:52:14 +0000 Original-Received: from localhost ([127.0.0.1]:45474 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gn4iD-0000Jk-VR for submit@debbugs.gnu.org; Fri, 25 Jan 2019 11:52:14 -0500 Original-Received: from mout.gmx.net ([212.227.15.18]:35665) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gn4iC-0000JX-4T for 34179@debbugs.gnu.org; Fri, 25 Jan 2019 11:52:12 -0500 Original-Received: from [192.168.1.101] ([46.125.249.96]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Mbxdm-1gW5YZ18kA-00JNtu; Fri, 25 Jan 2019 17:52:05 +0100 In-Reply-To: <83woms6ex9.fsf@gnu.org> X-Provags-ID: V03:K1:QrQBN3OiEzoTMGIQo22LXQaxbNxCkW7vkPfW2dqW/bq/JJOjMDS KEYLmqtKO7miDaLcP0H9ftZ9Rn2bLA0hXyof6qy9aN4gy1KS+J5BcVjsH/RtQOXxITFsNCA XwlJ688XYncBIAXNUgGCz1j+apwJhppiWVHuVzqE9NInmhsiHNzK41+hw1IzZ0ON7rrY5am Io9lgNamVIl2+slpLjymg== X-UI-Out-Filterresults: notjunk:1;V03:K0:re8GdtWlYQY=:v8KnAtC8IOpS9Lj8TkjGuk CW8mARN5QvtcZwWtxqkHpoT1F5Qmv453KBoFdF4M6cpS0RfujpJSqVzFEntSsMQ/U4Jwp6+pE bPUJs2IHyXLDKaL6YWf9ThgoylfxO87PfChl8/ndN3yTpYQYVTBo2Q7hxuggu2a1CGmlFw3mF ov+u3xP4h4g/PjOOFHj4WLvSjKcSONF/eWfhXEn/fyXKayi3REIqfDeSNXBU/Os75g644f6my leFSkrOoWyNYjxQZ9hAgZ+/WuSZ6Cpo5ubhQvjxCJ0W6CVtgVzK1S99kvYSsYixi2r0d8TOf8 MteyiMyfu9GZYW1vm9SdFhXsZjXOvXYm0A50NSg8ADlud1DsB1vecGMnl3n7WfzCkGExTElp/ +8zweDl62g3Icht5s5VvpeaMz4uT0wHwOXy7mNkx/HuQ0dvhmCThkpjn9UdHESY7oe5So/j1A spEZGOR5IpYxu9RUkATE3Yz5JxvGOt7abQdnZqHvdDtD3kzeT8lAe3fN2tXR0IaUaE+SrEZzS tugjceJWPWZTHusNdsB5JSxZT51UI4j3y7NWUfUZD3dCSVNfNl4fpsx/DeUBE7ErI8+tYdgL0 m5dgt0DXkMsLTc+CAPAIs65UAx44Uo2eOKWe/451ykl2le3E2PNqIkYDEml3CXQhz70VnCx8g jmlH0uB8GygLQESXR84YSvR6qYtr9zgCXX7SK66I12ZrB78Eko7NCPPqzyq4aF5MKukft9AyA tB5ccJN6OSAJ+UNkUPjL9Z0AbWywqbJvL5ZLGkKKyt73l5Nmlx08Wdl18sg4f716JOhRcvfX 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:154776 Archived-At: > You are right, but window-font-width called by > window-max-chars-per-line also calls select-window. > > Btw, I don't think replacing with-selected-window with > with-current-buffer will necessarily yield the same results. Right. I attach a more correct patch now that does not select a window in these cases. Michael, please check whether it fixes your use case. > And we > cannot in general forbid calls to with-selected-window in hooks called= > from run_window_change_functions anyway, can we? Certainly not. >> I can't get the hang with a single frame. Can you? > > OK, but does that change anything? Why is having a separate frame a > problem? That's what I would have liked to find out. >> It's an infloop triggered in =E2=80=98window-configuration-change-hoo= k=E2=80=99 and it >> was always easy to trigger an infloop there. > > Not sure I understand what you mean. The loop is in > redisplay_internal, not in window-configuration-change-hook. How was > it easy to trigger that in the past? And even if it was, shouldn't we= > avoid such a loop? Agreed. > In any case, it is way too easy to do in functions called from > run_window_change_functions something that sets > windows_or_buffers_changed, so automatically retrying redisplay based > on that variable after run_window_change_functions returns is IMO > dangerous. But what would be the alternatives? Having clients ask for redisplay explicitly every time they are in a hook? Or maybe just suppress redisplay_other_windows when running from the hook. Thanks, martin