From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.devel Subject: Re: Remove all existing file notification watches from Emacs Date: Sat, 16 Oct 2021 16:32:41 +0200 Message-ID: References: <87zgr9igqe.fsf@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40874"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Michael Albinus , Emacs developers To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Oct 16 16:32:25 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 1mbkjZ-000AMf-9z for ged-emacs-devel@m.gmane-mx.org; Sat, 16 Oct 2021 16:32:25 +0200 Original-Received: from localhost ([::1]:53272 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mbkjX-0006fi-Cu for ged-emacs-devel@m.gmane-mx.org; Sat, 16 Oct 2021 10:32:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39134) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mbkhb-0005eM-Ed for emacs-devel@gnu.org; Sat, 16 Oct 2021 10:30:23 -0400 Original-Received: from mail-pj1-f45.google.com ([209.85.216.45]:33648) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mbkhZ-0000hn-OR for emacs-devel@gnu.org; Sat, 16 Oct 2021 10:30:23 -0400 Original-Received: by mail-pj1-f45.google.com with SMTP id q10-20020a17090a1b0a00b001a076a59640so8748820pjq.0 for ; Sat, 16 Oct 2021 07:30:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GVSLErjK1rPogjfCiSKMIUb67UhPh8MDsSXwNjQ1Po4=; b=uIzQ0/vQnX9vy201b2nLLLaYibp9ITKI3tYk20/4XNk1SraEk2uAI5AB+36sGrEl+3 KM7jTWsQWSyi01/d4ZpLaJtWe7b8yjWW8phBc+gOXH7yTyFYgKDW93rboNdis/kIQwB/ qm8AnUpcSfyUB4bwYIwZkJWwMjiZ2S7n5f3TBJrrA6/1yDbMfNeHZ1df972g1exUs9cZ ov8cGcqrLXCdZjuM1yZdCM3nhRHbp1RZ3/5tmraM1EhWSzecjNbrToT/Kak95NYl7r8G tvcDi99WQEsRQDiiLVn3pprPe40yCIunUc58Hgmm+1AaLmOKT5RBI4GPLypjYrRGTg8Z TlSA== X-Gm-Message-State: AOAM532NilL/Vr3g+edtlDdaXSg4GRdb28LJhlYf9pOQAbvjJLdC4MSk S0F3jISy3oQbmn2pSMixgPXeBqqUWLssmgd2bKM= X-Google-Smtp-Source: ABdhPJzDS03IDLsgDOTkP+L+RrglVn8QsUycKdyez976X5BAScEJugEBAExlAJF5G1PJMObhqlYR2V3rVs59Gk47XQ8= X-Received: by 2002:a17:90a:460a:: with SMTP id w10mr35044466pjg.132.1634394619515; Sat, 16 Oct 2021 07:30:19 -0700 (PDT) In-Reply-To: Received-SPF: pass client-ip=209.85.216.45; envelope-from=stefankangas@gmail.com; helo=mail-pj1-f45.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no 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:277178 Archived-At: Stefan Monnier writes: > I can see its use while debugging but I can't imagine it being of any > use in real ELisp code because it's much too blunt. > [ Personally I'd put a `--` in its name and/or add some blurb in the > docstring explaining it's only for debugging. ] Would it make sense to have something like 'debug-elisp.el' where we could put all/most functions that are only useful when debugging? Then we would decrease the risk of users stumbling upon our sharper tools unless they actively go looking for them. In this case, I can imagine running this command by mistake or mistakenly messing up quite a few things in a typical user session. Orthogonally, could we place all/most such functions under some prefix like "debug-"? I'm not sure this makes sense, as I can't think of any more commands that fall in that category, but the 'bidi-display-reordering' variable is one candidate for a prefix, I think.