From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Boruch Baum Newsgroups: gmane.emacs.bugs Subject: bug#48408: BUGFIX: window-default-font-height: check for nil string Date: Wed, 19 May 2021 06:39:23 -0400 Message-ID: <20210519103923.gbraw4ieek3wu3cp@E15-2016.optimum.net> References: <83mtsxzund.fsf@gnu.org> <20210516030618.7caj6icukblavhbp@E15-2016.optimum.net> <835yzjwbnj.fsf@gnu.org> <20210516044215.23yd5ae3yeby6kaq@E15-2016.optimum.net> <83zgwvuu5z.fsf@gnu.org> <83tun3ur7h.fsf@gnu.org> <20210516065904.5wweuipi23oy5g2x@E15-2016.optimum.net> <83pmxrulm4.fsf@gnu.org> <20210519040053.7u7n73smu2hnczap@E15-2016.optimum.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8383"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: NeoMutt/20180716 Cc: 48408@debbugs.gnu.org To: martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed May 19 12:40:19 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ljJch-00021N-FZ for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 19 May 2021 12:40:19 +0200 Original-Received: from localhost ([::1]:36782 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ljJcf-0008FB-QK for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 19 May 2021 06:40:17 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59346) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ljJcQ-0008F1-MN for bug-gnu-emacs@gnu.org; Wed, 19 May 2021 06:40:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:46640) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ljJcQ-0005it-Ec for bug-gnu-emacs@gnu.org; Wed, 19 May 2021 06:40:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ljJcQ-0000lY-7S for bug-gnu-emacs@gnu.org; Wed, 19 May 2021 06:40:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Boruch Baum Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 19 May 2021 10:40:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 48408 X-GNU-PR-Package: emacs Original-Received: via spool by 48408-submit@debbugs.gnu.org id=B48408.16214207792911 (code B ref 48408); Wed, 19 May 2021 10:40:02 +0000 Original-Received: (at 48408) by debbugs.gnu.org; 19 May 2021 10:39:39 +0000 Original-Received: from localhost ([127.0.0.1]:58186 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ljJc2-0000ks-Ri for submit@debbugs.gnu.org; Wed, 19 May 2021 06:39:39 -0400 Original-Received: from mout.gmx.net ([212.227.17.20]:44117) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ljJbw-0000kb-Rq for 48408@debbugs.gnu.org; Wed, 19 May 2021 06:39:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1621420766; bh=4fBq7WK6JqAGdDZ5gHAc4bSXc0+hc7AEjwLwAOjAB3A=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:References:In-Reply-To; b=X6aVdOE+U0LZ7PNqgkxDFhipHbilaA5jW4Brgp1ZXW6Ui2qi3j2VIvq+cUraWuVbd 7DnqXG6rZYObF2trtifW7KhYBAST+uCZIOI6rinL4ZuWmepPx3MaEvIDQ5+POucgBy lKU059/+K+lW+HqGgCBfKLi8Ews5MPLinZvO5+u0= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from E15-2016.optimum.net ([96.224.230.212]) by mail.gmx.net (mrgmx105 [212.227.17.174]) with ESMTPSA (Nemesis) id 1N49hB-1lIx4O42Wv-0102ik; Wed, 19 May 2021 12:39:26 +0200 Content-Disposition: inline In-Reply-To: X-Provags-ID: V03:K1:E/t1X7N3c+hAlLmGr0H41+LTKOcgyAIRoZBKhWExIdg9nIGzH0w AikM4BQibFaYbV44aiw7aot1stXaVV9DCJOtTUlytOkvsgLEP59OA56JcMWg+wDdqILre4i COqZ4PgRT7hIB3WQ7/pr8Z57Zy60qSUtVnZLA12Nnffd64hQH12w9kz7zva1l7c2tElDIE3 rlPjzY3RaWIk0V2KJvztQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:jWc58jKoG+U=:P6T9L4Og3bmTvQNnhUBn0u hhFXYJztPFZ5hcaIWX3iRqIn6Aj9CJ9Aq1GAcN/xc01Wxd/IHA2EXUremr+ShY7pisdDNHFVe 38wEf2pEKD8r5/kenBBP+CoJHlmTAt23r/Z2YaVpphG2+FxQUSxWmcPsymOt/EbQqFmQvzXrU 5e9jiu10Qj3UE2lNZt7xM1RqREWs0RTOohz7gESlpcxBDWpA6CdZ4JXtpmf9VfXfKyo9oix+c wpaiUTlAtvTFPAzThnKcdp/QqD6/CKgGLcR9lPMud8Ldp0GsVTkCWU1m/7Qd2id+/s6Y+j8zZ t0s4vpINiQ9ZQdAdb3Q4KNNKVItT/UG5KwQUY2MFmgaOdS9FC7BWUFag2s4++CeCp8drlFMqN me2ihgpUn/qpDdwbg7k3cMvAmmkOsSmDiCKBopX6k1np18aouGWg4rc7I5GTtbdH6Lt/AY0oJ 9Wd88Rj5GQNdxaazHTek/BNvWCcuAdmDcieXmBI4l8jvulu+upckHwsJKBJbJzWD45dWd2QMm 1MD1t5cML0mARpB52EdO05g4/rRCev376yBVfbp61RZ8V2X8H9bd0Uik73Ez43palTDGkcHKT Vy0e/zCPbqavUMbIG2LlrxwOIuBKXSW3TmSIDboSKSXWf4mxv93es6PGFsKYQR0sU712wGzXk O2DNbGbS3x5E209cTEeiJ1z+Qc2s+AmQD7MC/O6K6BGIN1dJxbCJcqydWiy0ojFG7BzKQlA8H jkEmq4MkAr4MmWL0DLJDNc9cmLByK3b/cnQwPwtruc+hJsykgOFMpSxLUInhSDTXwH4ttPSm X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:206870 Archived-At: On 2021-05-19 09:45, martin rudalics wrote: > > 1) In working on this bug, I noticed that the mode line on the GUI fra= me > > was not correctly indicating the frame name. > > What do you use to indicate the frame name in the mode line? Nothing. It's however the default mode-line is configured. From the describe-variable page for `mode-line-format': ("%e" mode-line-front-space mode-line-mule-info mode-line-client mode-line-modified mode-line-remote mode-line-frame-identification mode-line-buffer-identification " " mode-line-position (vc-mode vc-mode) " " mode-line-modes mode-line-misc-info mode-line-end-spaces) > If you have a title bar, does it correctly display the frame name? Yes. > Note also that "the" mode line is ambiguous - with split windows a > frame usually has several mode lines. Performing 'C-x 3' does present two mode lines, both of which fail to identify the GUI frame. In both cases, the mode line(s) read(s): U:@**- *scratch* All of 0 (1,0) > > > 2.1) Whenever a minibuffer is active in one frame, the other windo= ws > > on that frame are navigable and operable. However, all elemen= ts > > of all other frames are completely frozen. > > What happens when you type C-x 5 o or C-x 5 2 in the navigable frame? Initially, I thought the system responded fine to either commands, but then got a shock. I used a GUI frame for testing the navigable frame, Pressed M-x, then C-x 5 2. A second GUI frame *was* created. However, upon performing Alt-TAB to have the underlying operating system (window manager, really) switch me to the tmux window in which I had prior emacs -nw frames, all were frozen and remained in their frozen state until exiting the minibuffer (The M-x on the GUI frame). What's more surprising to me was that when I tried M-x C-x 5 0 (yes, I misread your suggestion of 'o' as zero), the -nw frames also froze, even though the GUI frame no longer existed! I wasn't expecting that at all. To top things off, the -nw frames unfroze when re-launching a GUI frame (using the operating system's xdg-desktop method). When the -nw frames un-froze, they displayed the 'type-ahead' characters that I mashed while the frames were frozen. =2D- hkp://keys.gnupg.net CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0