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: Sun, 16 May 2021 02:05:12 -0400 Message-ID: <20210516060512.sx3go2zr35izujlo@E15-2016.optimum.net> References: <20210514011519.vsy5jbhyxd4v6kpt@E15-2016.optimum.net> <83mtsxzund.fsf@gnu.org> <20210516030618.7caj6icukblavhbp@E15-2016.optimum.net> <835yzjwbnj.fsf@gnu.org> <20210516044215.23yd5ae3yeby6kaq@E15-2016.optimum.net> <83zgwvuu5z.fsf@gnu.org> 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="9176"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: NeoMutt/20180716 Cc: 48408@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun May 16 08:06:13 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 1li9un-0002DV-CZ for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 16 May 2021 08:06:13 +0200 Original-Received: from localhost ([::1]:41640 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1li9um-0001Gc-DE for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 16 May 2021 02:06:12 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41092) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1li9uf-0001GR-GK for bug-gnu-emacs@gnu.org; Sun, 16 May 2021 02:06:05 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:38027) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1li9uc-0001fy-3j for bug-gnu-emacs@gnu.org; Sun, 16 May 2021 02:06:05 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1li9ub-0006Vf-VL for bug-gnu-emacs@gnu.org; Sun, 16 May 2021 02:06:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Boruch Baum Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 16 May 2021 06:06:01 +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.162114512424979 (code B ref 48408); Sun, 16 May 2021 06:06:01 +0000 Original-Received: (at 48408) by debbugs.gnu.org; 16 May 2021 06:05:24 +0000 Original-Received: from localhost ([127.0.0.1]:49573 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1li9u0-0006Up-4J for submit@debbugs.gnu.org; Sun, 16 May 2021 02:05:24 -0400 Original-Received: from mout.gmx.net ([212.227.15.15]:38361) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1li9tx-0006UX-OM for 48408@debbugs.gnu.org; Sun, 16 May 2021 02:05:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1621145115; bh=YZUpAIkuQG8meOw70aOZpZrJUAdRDQZtOt5EPjN9AaE=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:References:In-Reply-To; b=Y2IJtfIpB3L7vMhvDSx7h/lsvJcwGIwZj99M8ul2aF/WHsymUwCN/pTwBWf3mR5aU t7WufeUHXViTt1zl9T7IAz9WCRgISrJFd2jtbR7MURJNDxdMWfSS6kCLhV8z/E+uhU eJX2ibWS6DwvKjbsUtfNI8rgt8ciYXPYclcD6Gzk= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from E15-2016.optimum.net ([96.224.230.212]) by mail.gmx.net (mrgmx005 [212.227.17.184]) with ESMTPSA (Nemesis) id 1M3DJv-1lljrq0lUD-003gl0; Sun, 16 May 2021 08:05:15 +0200 Content-Disposition: inline In-Reply-To: <83zgwvuu5z.fsf@gnu.org> X-Provags-ID: V03:K1:q6w9jgl30BIfNA9CDs7wL1FWMll4P/T2JZ/TL9b54nN/2C7fM62 VueiAIQHEwxYQZD9Ph7pkIBCWZF/1rDZsBjZsFFId5rl2+5i4e/6UjHPCpMBdzqR52XR+1w GmT3rtTNF5HXxvUeY8u1okEviW45DlcfBn/vc96buHWDOLLDiHToxFs2SMJRRIUFpk1DHre n+J891R2P8wVka8z8DHwA== X-UI-Out-Filterresults: notjunk:1;V03:K0:WBV9SmH/R20=:ApkqOAD0RsQkMP73Jo/Orp V8djfNpKwhL/aUJ5+AwXJ2lbbJEpZxhLnoO/BCseLxDZL6a6hL1KhG2QdB4Os6CyLN/DNtb9e JxEGahvH8vKoEuU7fIzQpKFnGgO9Ou6KjaWnY5Sz+y/HxKBrlFYAT8ezQigpz4j+bOLpE3KgY aS3aLDstbzyhM6zm63tDyp3m55uJfrSDnhKu/M+2zBRTS49kbsUiV3rpzFKb4dDollcM5rW5B uTCPyXzP8lBtmHUH7qwN1zlNE3fNvsF3/fHPzLyA4OgnevbMfeSIOHt8yllYX7fxwzkZ1K9QE c8/ouwY0OyszITFIe06ieCt+mnN9cOIrqFrdDCgJa9F8pRhAylOB/itNpx/zwnqpthdkRdieH 0g+RIHaE0nCwrFRIbwwwhSMRN3IX/uzUUx0x3xZFMXmQh8ghUGy09EWwE0QoOJUzVFXG+kpSl zvfsgwvj+ZGozhAFKaihjeOznMzk1xkNYAQU1T0kU+AmXxz15ccAoqTxNHMUPaHB+AqGm7aEK YNRGyT33B5RzpokarC96DxJktOpfSIgIIMy0MNuGyzc5B3oVWFssV0FDx8vrtUbFAapfesDkl wpZpsCcYgryf1PDA/OSpNvBYGXGQp08AHbPHNi73JwFuJYjEVbeYxcMUnLpRxpsz2tmSosEOE 1DxUJWVskPy72m4IG7Llak71U/ovjPy1opKhuQmugC1qqjc2mLTe0BEmTU81eOpuwRRvJpifn 3bTx5ig/Nzb0Alqpz5bGJVqVkWAwRScK8HM36qz+1hw7ySzhpCdrvuLgKQjThZIi5x/SnhWc 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:206636 Archived-At: On 2021-05-16 08:25, Eli Zaretskii wrote: > > Date: Sun, 16 May 2021 00:42:15 -0400 > > From: Boruch Baum > > Cc: 48408@debbugs.gnu.org > > > > On 2021-05-16 07:22, Eli Zaretskii wrote: > > > (terminal-live-p ":0.0") > > > > on tty frame: nil > > on gui frame: nil > > > > > (framep ":0.0") > > > > on tty frame: nil > > on gui frame: nil > > > > > (frames-on-display-list ":0.0") > > > > on tty frame: (#) > > on gui frame: (#) > > Thanks. So you have just one frame in that session, which is a TTY > frame? I thought it was a session with both GUI and TTY frames, is > that not so? I have several frames: at least one is definitely a gui frame (ie. it appears in its own gui 'window' after being created via a gui menu which seems to have accessed a gui emacsclient.desktop file), and at least one is definitely a tty frame (ie. my original 'emacs -nw' invocation, from within tmux). In performing the final test again: > > > (frames-on-display-list ":0.0") on tty frame: (#) on gui frame: (#) So the output remains the same, but what you didn't ask me to report was the mode line output, which differs: on tty frame: -UUU:@**--F139 *Ibuffer* on gui frame: -UUU:@**-- *Scratch* Yes, the mode line displays a frame ID different than the frames-on-display-list output. Frame 153 does exist: It is the frame created by my email client (mutt) to compose this email message). So, it would be the most recent tty frame created, although the GUI frame was created after. Changing buffers on either frame does not alter the mode-line output for frame. Performing 'C-x 5 b' (M-x select-frame-by-name) on either gui or the non-mutt tty frame only offers one completion candidate option: F139. The mutt tty frame offers the single completion candidate F153. Manually create a second frame on the non-mutt tty (C-x 5 2, C-x 5 ,foo). Perform M-x select-frame-by-name again, and on the non-mutt tty frame get two completion options: F139 and foo. On the mutt tty frame, just F153. On the GUI frame, although the mode line hasn't changed, the only completion candidate is 'emacs@E15' (E15 being the device hostname). This completion candidate never appears in the tty frame. > Anyway, the above probably means we set up frame parameters > incorrectly somewhere. Hmm... Can you reproduce this? =2D- hkp://keys.gnupg.net CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0