From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Remove all existing file notification watches from Emacs Date: Sat, 16 Oct 2021 10:09:50 -0400 Message-ID: References: <87zgr9igqe.fsf@gmx.de> <87r1clhzaq.fsf@gmx.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24470"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Michael Albinus Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Oct 16 16:11:44 2021 Return-path: Envelope-to: ged-emacs-devel@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 1mbkPY-0006AO-EL for ged-emacs-devel@m.gmane-mx.org; Sat, 16 Oct 2021 16:11:44 +0200 Original-Received: from localhost ([::1]:45608 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mbkPW-0000do-Gy for ged-emacs-devel@m.gmane-mx.org; Sat, 16 Oct 2021 10:11:42 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35708) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mbkNq-0008Fp-0Q for emacs-devel@gnu.org; Sat, 16 Oct 2021 10:09:58 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:5529) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mbkNn-0007e2-Hs for emacs-devel@gnu.org; Sat, 16 Oct 2021 10:09:57 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 674CA100355; Sat, 16 Oct 2021 10:09:53 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id B23DF1001C8; Sat, 16 Oct 2021 10:09:51 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1634393391; bh=ejveegIdbb78xzGB3ufiCcQ9ydNhyr/khcUSF2gEd5I=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=QhnUp5o1tFLvGK+1UaaqX8Qwui5w6iFIg3gwSbSqHUgdkzz7jrYiVknNOGs1ywk2y Tf/Ohs0YqobB8PN5Zg1xAUa2MQV6K+VVChePmMPH1O8uEBIKiDPlBU2DK4jiRV/EXE LYPDhkeONIVZqVcE/l2+674S9wjqWf4wO2Po5zSRO5XQNDUWpSRv6X1KucGWZzkGb2 k2s7IWDPES/24fUie0/Av8eUt2zma//HP5dhqaV5WYM7KjyQb7WjgZ0cUnzio876y+ SjZpmztlRbDTpNGGCOmqQvPRzdI2w/4KYUPC0xoidbEaa+HGndtk7rASiv/X6Ta8qJ o8BY/BT9Hwasg== Original-Received: from pastel (unknown [45.72.241.23]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 7038C1201B4; Sat, 16 Oct 2021 10:09:51 -0400 (EDT) In-Reply-To: <87r1clhzaq.fsf@gmx.de> (Michael Albinus's message of "Sat, 16 Oct 2021 15:30:53 +0200") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:277175 Archived-At: >> [ Personally I'd put a `--` in its name and/or add some blurb in the >> docstring explaining it's only for debugging. ] > > Nope. There have been bug reports in the past, that Emacs was stalled > after creating hundreds of file notifications. One solution is to > stop/restart Emacs. The other solution is this command. That qualifies as debugging for me ;-) I mean, using this instead of restarting Emacs may work sometimes, but it can have undesirable (and hard to predict, for the end user) side effects since packages have had their watches killed from under them. So it's OK to use when the alternative is to kill Emacs, but it should come with some warnings (in a pessimistic scenario I can see some blog mentioning this command alongside the usual "set your GC threshold super high" and a few other things, in the toolbox of "make your Emacs more faster"). Stefan