From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.bugs Subject: bug#11017: 24.0.94; emacs-lock--kill-emacs-query-functions should ding Date: Tue, 22 Mar 2022 00:02:59 +0100 Message-ID: <87wngmx61o.fsf@web.de> References: <86mx7i79lb.fsf@web.de> <86obrxuz7p.fsf@web.de> <86fwc740a1.fsf@web.de> <87eemxq0a2.fsf@gnus.org> <87363dxul6.fsf@web.de> <87imc8ss7u.fsf@gnus.org> <87ils7nfku.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="7895"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Juanma Barranquero , 11017@debbugs.gnu.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Mar 22 00:04:12 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 1nWR4O-0001oO-8q for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 22 Mar 2022 00:04:12 +0100 Original-Received: from localhost ([::1]:55470 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nWR4M-0002r0-Q0 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 21 Mar 2022 19:04:10 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:46092) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nWR4F-0002qp-9Q for bug-gnu-emacs@gnu.org; Mon, 21 Mar 2022 19:04:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:44825) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nWR4F-0000Dc-1Q for bug-gnu-emacs@gnu.org; Mon, 21 Mar 2022 19:04:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nWR4E-0003cc-Hb for bug-gnu-emacs@gnu.org; Mon, 21 Mar 2022 19:04:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Michael Heerdegen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 21 Mar 2022 23:04:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 11017 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 11017-submit@debbugs.gnu.org id=B11017.164790378813817 (code B ref 11017); Mon, 21 Mar 2022 23:04:02 +0000 Original-Received: (at 11017) by debbugs.gnu.org; 21 Mar 2022 23:03:08 +0000 Original-Received: from localhost ([127.0.0.1]:38722 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nWR3M-0003al-Dy for submit@debbugs.gnu.org; Mon, 21 Mar 2022 19:03:08 -0400 Original-Received: from mout.web.de ([212.227.15.4]:39821) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nWR3K-0003aE-VQ for 11017@debbugs.gnu.org; Mon, 21 Mar 2022 19:03:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=dbaedf251592; t=1647903780; bh=f5WAM0rUag5J8sn30WHARldO30FCiDqSLqrBVb8Wx3k=; h=X-UI-Sender-Class:From:To:Cc:Subject:References:Date:In-Reply-To; b=iRors7yw6DQbXsGOMWiAfjsJ6+KsIJWJBEI7RarFdXtfPLLI4o561TBu1Ixj4Bqlm CILOHAzuk5mFdci+h8tNlPPpgDQtYmiYfJqdiLNfyx2wwD8h0BwqaGXnfkZpHnEHvf BivMmvNyZ+tAxhW3N4yRDbPLNPQRRCJxZbam66hY= X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9 Original-Received: from drachen.dragon ([84.60.174.212]) by smtp.web.de (mrweb006 [213.165.67.108]) with ESMTPSA (Nemesis) id 1MN6BN-1novPF0upB-00IsXp; Tue, 22 Mar 2022 00:03:00 +0100 In-Reply-To: <87ils7nfku.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 21 Mar 2022 22:47:13 +0100") X-Provags-ID: V03:K1:8nYBjzyF5CN9dHeSKsHKxIzoNHOp4//EkYeJQMEB3/0GOg/ASv5 ptKxTbDe4nDn6n84TiI9d4vP513zBIYw7cz2/WzCVl7q5eNl1TOFlF251uSePxqvzFB31Xj 4N7AtoMinTePSR2OJ6Tb+1T8IK06vlppe7+M2LdmNy2SfcTfZNIs+L+kuWOuicBU5Tc110n JaZUbMIsynBjOQxiKXomQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:M9lCynEN/iM=:83jStsJbCv1IqJMw176k/Q azsU/Z6ACdg+zxBhWaUs4TAaJnRBqIP/m+yacK3aMqQVME1cvq6h7r/hWKqKcvbnmqIi7KOb6 8yJHNwgbfjJx6gHkkWHF4xmznHNCgcVNDvhslgIyzYI+HVtU+eu+6qWdkowncC2drIkkKxqZL W8tVX3qF7p598cxzLNGxBMKlSCnXJutZtXwSeeL6A6ydid/4JNRU50CpjBIGHJISApNs4D4V8 8YpKcyIbg5vVydiD38f1HNJg5ct00P98Sb9q+aiTHsZp2FHuBD9hWEClunhBRjAnaibFzVuQ1 WFQDM+emKqJhG1Yah3klO8gCYGs8ZAAK+h/ECpGPVKXuBIr1KOblyztKNyXkXb0YWDvDYVETL o0akHclcl7G7MnznWcXvjfXE+12q2DCeCSJz05MtFEaM4BtTpv+YZ4TVSA2sOtICbYNJPZXpy ch8OdkWGf0Zt/p9Y4RYgDqmuVfzrU00VZtaLZvUeUXv8aLlgpiwKO6YiRTdqWjOptUp6KTZaH redrmOoxi4y18vqUdHR2AUai4wyK+dO9WZdJQPbpvF185j/MwUtD1cxV0BLpRAif9WuUawyiN eYvEXIHm0C4pneqFvSJMGNfTfRUdUhvXk3QNSYprHPuOWbK6tJ/GenI0w4kp1X5DQvkF6jiqS wscfAQfuPnOCNcwjH8xBCcnaFLaTR1y6pPOemNa57NI/o7jj1gkjqt/XxpmfXaIrghEhX9/u2 TPRPlcFpBS3Z1ByC+x/AUOE3Bvcsz/gGwbguZr4PsfY+vmLMy1pKmUDCH3LvLzCTYIczWnUs 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:228728 Archived-At: Lars Ingebrigtsen writes: > Looking at this again -- this is really `emacs-lock-mode'? > `lock-buffer' does something completely unrelated. Indeed. We were never discussing `lock-buffer', this is all about `emacs-lock-mode'. > But this is a minor mode, so the prefix arg is taken. It is also already taken to set the "locking mode"... ;-) > We could add a `emacs-lock-set-reason' command, but... would anybody > use that? I would not, this would be too distracting. Using the prefix arg of the mode function, or a function in the mode hook that would prompt automatically would be better. But I still think the feature is useful in general. When I'm getting distracted by some other stuff, I want to know why I had locked that buffer that prevents me from exiting. > I've never used `emacs-lock-mode', so I don't know what people er would > use it for. I'm testing master for a long time now so I don't rely on locking currently. Locks don't survive crashes. People don't use it because it's not really cool. Michael.