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 07:55:37 -0400 Message-ID: <20210519115537.x3dffxsmjolnpeum@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> <83cztnq7v6.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="36142"; 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 Wed May 19 13:56:11 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 1ljKo7-0009BM-4n for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 19 May 2021 13:56:11 +0200 Original-Received: from localhost ([::1]:49248 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ljKo5-0007vS-Qp for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 19 May 2021 07:56:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47034) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ljKnx-0007vI-Tt for bug-gnu-emacs@gnu.org; Wed, 19 May 2021 07:56:01 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:46723) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ljKnx-0001OC-MA for bug-gnu-emacs@gnu.org; Wed, 19 May 2021 07:56:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ljKnx-0004sF-LH for bug-gnu-emacs@gnu.org; Wed, 19 May 2021 07:56: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: Wed, 19 May 2021 11:56: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.162142535018713 (code B ref 48408); Wed, 19 May 2021 11:56:01 +0000 Original-Received: (at 48408) by debbugs.gnu.org; 19 May 2021 11:55:50 +0000 Original-Received: from localhost ([127.0.0.1]:58269 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ljKnm-0004rl-H4 for submit@debbugs.gnu.org; Wed, 19 May 2021 07:55:50 -0400 Original-Received: from mout.gmx.net ([212.227.17.22]:42329) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ljKnk-0004rV-QC for 48408@debbugs.gnu.org; Wed, 19 May 2021 07:55:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1621425342; bh=gZUE0gu+8Ya/jvbIyzlBCTSnekCIbuT3iQNghlqh23Q=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:References:In-Reply-To; b=Yb+c7QHPiUBAy579FnS0Tb2TayJJJi5GwxeY0fd0uih2LHtojuAwlbTCD9HlKOyw0 AlKqYAGT/xkAUkKYP26/QnMG89GheZuru/5DtxqeMBJJ5hs2gs0/QSP0ObLyxSG9kj cXjVdaPEOVt3NBLotV6v18IS9sZ18auDYrDKkaWo= 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 1M1ps8-1llWej2x4q-002HOj; Wed, 19 May 2021 13:55:42 +0200 Content-Disposition: inline In-Reply-To: <83cztnq7v6.fsf@gnu.org> X-Provags-ID: V03:K1:DkWGpCACjj41CsZuzbSFacyCpefVszmFEFDJWiwWRRdYJwwe0dy hYbqEWMo3MCl22lQGXZgpxvLOIKjBXxRzfXs9mcsny00fLnAmWTX3ATXxGl1VR2EO3YcG4i 0md5shhzsydm6B8E/WS8VUogj4J3Sh/lSDRo1Yh+UsZZzzkALAcHZbhXuW1SVqVPujuqnv+ moIIVigw4ArcJTiCbICZg== X-UI-Out-Filterresults: notjunk:1;V03:K0:MwOpkWgHdWo=:JvMGoGE+esn5l/JTTRoI2+ Ncu2tO/fEGwOIoU7Ed3s889v4vIPUzFs0E/QSkXWvTkpMuNEtaM0QKaFJXK3dzixK+uh6wgtl aTxS1F5mqUyw1h7WWBDTQXTEFLofLdOG079V/Z/tFZdimfrutZknNLDMoGLLmtCUVrBAKR51q gm2IGc0LYxew8F0xqcMfDb8uYgptx7Tsba/Jr8q8whI+smDbHHGYA1jfA4X6rXXM3Up6xey3J MW9193Jj6JfJMen2rCU4aD+Vyq37diPWHIace5qHcBPPYhMakf8TTmVeUEmaAJ/BJaD06Iw9b Ttcy2TdXxoV0E0zy0Jioxm5bJlfZQdAftNd47NaiOxEozYrfGuNIUujn+mw6xAe6fp6jcGvfJ sukgF+EoT0YXBIvqpuvaytxqL8U1QCQGwd4E+A+rtKqFyG7ui4NC69pjOMhJU92CYvj2epWkJ vk3k76lAwFXPxFUDMb/PDI4k8M9N5eyb5XMNv8Uk4oqZ5hSFHRHhs/0CUKKQa4gzbqISupXvo WCDT9Zo/CtGenUeCf58+QdARclcexn9fgWI7V3yUBCasH31mM5e+7QUFahst8hF2i7NzCJNjh 9OoezAuNhmvZEQd+8Yi5pffSLPMHWmbhMISXj0GFkL0fGtCzu4CvSArhZ3OsQT8P2Z1FcomEm g2WNTlDLwvBLmbKTqMXqs9kUJz8OsefuUah9ety1cagMgKH378Txy2+5Sx5vteolJxaRrgeOH uJ0nA4t4AMmlM51kGvzkzHyyYrfZz75BVxu8bT74pgtmI6Dgh8R2nT1aEL/SPe+8d3DnN31c 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:206874 Archived-At: On 2021-05-19 14:29, Eli Zaretskii wrote: > > Date: Wed, 19 May 2021 00:00:53 -0400 > > From: Boruch Baum > > Cc: martin rudalics , 48408@debbugs.gnu.org > > > 2) Likewise, for more than two years I've intermittently been having a > > 'grave' emacs bug that I never reported on this list because I > > couldn't ever figure out how to reproduce it. In working on this bu= g, > > I seem to have figured out the problem (but not a solution): > > > > 2.1) Whenever a minibuffer is active in one frame, the other window= s > > on that frame are navigable and operable. However, all element= s > > of all other frames are completely frozen. > > > > 2.2) This most commonly seems to have been happening to me when > > composing an email message using mutt, which I have configured > > to use emacsclient as its editor. > > > > 2.3) Up until now, my work-around has been to `pkill emacsclient` a= nd > > restart the client (this doesn't cause any data loss, since al= l > > data is on the server). > > It's a "feature": Emacs can read input only from one frame at a time. Without that feature, the emacs 'server' functionality could be useful for >1 physical 'seats' (in X11/Xorg terms) or >1 separate IP addresses by >1 individuals. There had been attempts in the past at some FOSS version of 'collaborative editing' (eg. gobby), and I thought emacs had that covered with its server/client option. I'm looking at the emacswiki now ... and as so often the case it seems very out-of-date. I don't personally have any immediate or foreseeable need for collaborative editing, but is there a 'recommended' method? =2D- hkp://keys.gnupg.net CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0