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#50849: 28.0.50; Proposal for Emacs daemon to signal when being busy Date: Fri, 02 Sep 2022 15:02:58 +0200 Message-ID: <87sflaszct.fsf@gnus.org> References: <86czouksh2.fsf@protected.rcdrun.com> <83mtnykpij.fsf@gnu.org> <87tui5fdku.fsf@gnus.org> <83y27hjhy2.fsf@gnu.org> <87r10uvxr9.fsf@gnus.org> <83o7vyowcl.fsf@gnu.org> <87czceufj1.fsf@gnus.org> <83ilm6osqz.fsf@gnu.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="3681"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: bugs@gnu.support, 50849@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Sep 02 15:04:17 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 1oU6LH-0000mp-W7 for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 02 Sep 2022 15:04:16 +0200 Original-Received: from localhost ([::1]:37484 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oU6LG-0006yc-S1 for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 02 Sep 2022 09:04:14 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48098) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oU6L4-0006wK-DE for bug-gnu-emacs@gnu.org; Fri, 02 Sep 2022 09:04:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:55525) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oU6L3-0004vw-RW for bug-gnu-emacs@gnu.org; Fri, 02 Sep 2022 09:04:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oU6L3-0003pG-LK for bug-gnu-emacs@gnu.org; Fri, 02 Sep 2022 09:04:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 02 Sep 2022 13:04:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 50849 X-GNU-PR-Package: emacs Original-Received: via spool by 50849-submit@debbugs.gnu.org id=B50849.166212378914630 (code B ref 50849); Fri, 02 Sep 2022 13:04:01 +0000 Original-Received: (at 50849) by debbugs.gnu.org; 2 Sep 2022 13:03:09 +0000 Original-Received: from localhost ([127.0.0.1]:45271 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oU6KD-0003nu-GO for submit@debbugs.gnu.org; Fri, 02 Sep 2022 09:03:09 -0400 Original-Received: from quimby.gnus.org ([95.216.78.240]:35702) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oU6KC-0003nf-4E for 50849@debbugs.gnu.org; Fri, 02 Sep 2022 09:03:08 -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=U3KfvqtXLiEPkkEhWKQQFQIPFk0mkcnKmg5tI2eb8h0=; b=tYpi2jF0bvrDzoaRAKe71plkog 4qrQ34MH/SXeVrcb71th0fuFpT+rw4iLEM1tOpeF81qYwf1+mPz+Lhf6wL6FFRGNyH2woUm9AWP0S Ek39KkcNKob8MMRQf81ZgO+4jdXomHII9Kjh6r39IjL46KgrUiAmtXEuOvlgkY9MY6gA=; 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 1oU6K3-0005gj-1Y; Fri, 02 Sep 2022 15:03:01 +0200 In-Reply-To: <83ilm6osqz.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 02 Sep 2022 15:39:16 +0300") Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAABGdBTUEAALGPC/xhBQAAACBj SFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAAElBMVEV9coBFLl4VFRWx raft7Ob////o4EvwAAAAAWJLR0QF+G/pxwAAAAd0SU1FB+YJAgw7Jkx1a2QAAAGKSURBVDjLlZRb doQgDIZFXIDGWYBkugA1WYA27H9NDQG8TOtDMwcO5uNPwm0aN/xtzSfI343+7tabo3dFoR0igo4C DgDaJYUnonnFmwUDnjy1d4AGGj/DMdFdgC8fofENlTkJNEv2T0S+7wcHhyLHn2ZnpeHwAd7wK3ku 1XrAcf8A7zVld9rOHHOqKKwYOG5u6fYDkM4JOpZoJidYrdhYrQLdKpW8D/9FQbrE6QCXHKR7GA6Q AvsSKpEDaNxRqoJm7DS6vCzFSCcg0OzSviwFZ2B+3e5UkLYWUKeeCoIupxggaKh0KbxkSRc5igaB cFcQK8jL8yWHRHWrzCJtyZ8VxDafZi7L66hWFZkTtewtgqdogFmiWA4zlo4kA/VHEpa6J50UkCQc z/MYVWUgljXr4mysZZ7A0JZPRbVXYEdkpzKzVJCYtm90VX5RAMe127/kCmYIem8DY9zr0ed11As7 icOs3wyUZxYw9Bu+UqDFbgmfz2yC9ByGcn0Y/7AElicATwCfwMOfzL/BD8VDqPeEMP8PAAAAJXRF WHRkYXRlOmNyZWF0ZQAyMDIyLTA5LTAyVDEyOjU5OjM4KzAwOjAwtl6N/QAAACV0RVh0ZGF0ZTpt b2RpZnkAMjAyMi0wOS0wMlQxMjo1OTozOCswMDowMMcDNUEAAAAASUVORK5CYII= X-Now-Playing: Brigitte Fontaine's _Comme =?UTF-8?Q?=C3=A0?= la radio_: "=?UTF-8?Q?L'=C3=A9t=C3=A9_?= =?UTF-8?Q?l'=C3=A9t=C3=A9?=" 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:241340 Archived-At: Eli Zaretskii writes: >> What would be a reasonable timeout here? Say... five seconds? > > Too short, IMO. I'd say 10 (and expose this as a Lisp variable, so > whoever is unhappy about the default can do what they want). Makes sense. But I'm slightly leery about having a default timeout at all -- I can imagine that there are people using emacsclient as an RPC thing to control an Emacs automatically, and in that case, any timeout would be wrong: It's more important to have a reliable mechanism than anything else. (And in that scenario, the Emacs daemon might well be busy for a long time, if you have a script that just feeds commands to the daemon...) But on the other hand, it's nice to give the user some more feedback there than just hanging. Hm... Might it make sense to use the timeout to just output a message on stdout saying "Unable to contact the server; use `C-c' to break" or something? Instead of just exiting/erroring out? Anybody have opinions here?