From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#51490: Show an indicator when Emacs is busy somewhere in the Emacs window Date: Mon, 19 Sep 2022 22:16:48 +0200 Message-ID: <87r107nmq7.fsf@gnus.org> References: <875ytmbnk2.fsf@gnus.org> <83y26i34e1.fsf@gnu.org> <87wnm27b57.fsf@gnus.org> <87sfwq75q4.fsf@gnus.org> <87wnm22q7y.fsf@gnus.org> <83ee8a2pm7.fsf@gnu.org> <87fssq2orj.fsf@gnus.org> <87pmru18xg.fsf@gnus.org> <87lf2i18pv.fsf@gnus.org> <87h7d618j7.fsf@gnus.org> <87bl3e2m1y.fsf@gnus.org> <87pmrtz1y7.fsf@gnus.org> <83pmrt1bsa.fsf@gnu.org> <87y26hxm8a.fsf@gnus.org> <87k0hvviiu.fsf@gnus.org> <87a6iqr8il.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33709"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: 'Eli Zaretskii' , 51490@debbugs.gnu.org To: Stefan Kangas Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Sep 19 22:17:22 2022 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 1oaNCj-0008Uk-F6 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 19 Sep 2022 22:17:21 +0200 Original-Received: from localhost ([::1]:52044 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oaNCh-0004WH-J1 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 19 Sep 2022 16:17:19 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54642) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oaNCQ-0004Q0-Uf for bug-gnu-emacs@gnu.org; Mon, 19 Sep 2022 16:17:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:56295) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oaNCQ-0006Tk-ME for bug-gnu-emacs@gnu.org; Mon, 19 Sep 2022 16:17:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oaNCQ-0003np-HL for bug-gnu-emacs@gnu.org; Mon, 19 Sep 2022 16:17:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 19 Sep 2022 20:17:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 51490 X-GNU-PR-Package: emacs Original-Received: via spool by 51490-submit@debbugs.gnu.org id=B51490.166361861914596 (code B ref 51490); Mon, 19 Sep 2022 20:17:02 +0000 Original-Received: (at 51490) by debbugs.gnu.org; 19 Sep 2022 20:16:59 +0000 Original-Received: from localhost ([127.0.0.1]:55372 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oaNCN-0003nM-3y for submit@debbugs.gnu.org; Mon, 19 Sep 2022 16:16:59 -0400 Original-Received: from quimby.gnus.org ([95.216.78.240]:37786) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oaNCL-0003n7-1v for 51490@debbugs.gnu.org; Mon, 19 Sep 2022 16:16:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:Date:References: In-Reply-To:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=XRfB6++Zck1PVmE6Ymb9hhXwZmS85ldhac94wmWw4+Y=; b=SbqhVi6PNBOT6iaJqbBJJDaN3w XT5Ny5lVoemRi04SoC0dcYrzNuyZWfgkgCz9JQfetXomROjxUXwBRLgTOFYVc5vyerKN/XWwNMIqO 4h8aWUp19lrjwZgTJPGCffV3yTBFL1Yi26oLTtgu3DABhAC7iv/WLZTP0dxVgz3ZF/8U=; Original-Received: from [84.212.220.105] (helo=joga) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oaNCC-0003gH-FU; Mon, 19 Sep 2022 22:16:50 +0200 In-Reply-To: <87a6iqr8il.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 30 Oct 2021 14:40:02 +0200") X-Now-Playing: Akkord 's _#savefabric (11) (Mixed by Second Storey)_: "Scalar Wave" 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:243128 Archived-At: Lars Ingebrigtsen writes: >>> I'm not at all sure whether there'd be any negative repercussions to >>> spinning a glyph in the mode line area (for instance -- what about if >>> you're running over a slow ssh connection?), but perhaps it's worth >>> exploring and see how goes? >> >> Let's continue discussing this as a new bug. > > I wonder whether this could be implemented by modifying the glyphs in > the mode line directly instead of going through the entire mode line > machinery (for efficiency). I was thinking we'd designate (say) the > first (or last) displayed position on the mode line as "the spinner" > (and restore the previous glyph there after finishing spinning, of > course). Eli, does this seem like feasible approach to you?