From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#56311: [PATCH] new function: delete-visited-file Date: Sun, 03 Jul 2022 09:04:31 +0300 Message-ID: <83zghqag0g.fsf@gnu.org> References: <83k08y67ml.fsf@gnu.org> <87wncyr7st.fsf@gmail.com> <87wncybg4z.fsf@gnus.org> <87r136aze3.fsf@athena.silentflame.com> <831qv5fk7t.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15126"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, visuweshm@gmail.com, 56311@debbugs.gnu.org, spwhitton@spwhitton.name To: Zachary Kanfer Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Jul 03 08:05:10 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 1o7sjF-0003mD-SQ for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 03 Jul 2022 08:05:10 +0200 Original-Received: from localhost ([::1]:38336 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o7sjE-0008Kq-Dh for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 03 Jul 2022 02:05:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35306) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o7sj8-0008Ki-B2 for bug-gnu-emacs@gnu.org; Sun, 03 Jul 2022 02:05:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49253) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o7sj8-0003Yc-1r for bug-gnu-emacs@gnu.org; Sun, 03 Jul 2022 02:05:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1o7sj7-0001rE-MI for bug-gnu-emacs@gnu.org; Sun, 03 Jul 2022 02:05:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 03 Jul 2022 06:05:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56311 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo patch Original-Received: via spool by 56311-submit@debbugs.gnu.org id=B56311.16568282937121 (code B ref 56311); Sun, 03 Jul 2022 06:05:01 +0000 Original-Received: (at 56311) by debbugs.gnu.org; 3 Jul 2022 06:04:53 +0000 Original-Received: from localhost ([127.0.0.1]:43150 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o7siy-0001qn-RC for submit@debbugs.gnu.org; Sun, 03 Jul 2022 02:04:53 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:50328) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o7siw-0001qZ-Mw for 56311@debbugs.gnu.org; Sun, 03 Jul 2022 02:04:52 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:33232) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o7sir-0003WR-7T; Sun, 03 Jul 2022 02:04:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=Jozq5/5OqqO4SM9uI6wI4+Nf/TiOkezw3VqUANig9MA=; b=Qz4UUfaaD/zu sYNRWtnCrOOvAtIpA+4DE5b9lqhvxf8JL8sUHGPLN7rFSZgerpqoWnXMN7MSkYZeCUxrda8+3ULTt zWXnp0jWFpaucR1v/jsrFtJm+2S8LOiaHhtxO4deMPZcy6oDfcZV6wuWRbl8FtFOlyck/pNJJQ0B1 0O2U9OE3N2Pk5CUXcg+5LK+5Bhyy7HgP+rYtxDBdypHbvO3GQX9vo4wV25u7ycsZENkn41r+4FKfW sDaO1wZw/OEV2iBqMBmii5CeRjXKIhEkgZOAE8g6fc1FmAKmxYzYMDgS6McKxDmoNEtDbHfS7XntK gIVnXYpAEwIalaOs2GbkZg==; Original-Received: from [87.69.77.57] (port=1072 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o7siq-0000L5-Ko; Sun, 03 Jul 2022 02:04:45 -0400 In-Reply-To: (message from Zachary Kanfer on Sun, 3 Jul 2022 01:06:40 -0400) 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:235964 Archived-At: > From: Zachary Kanfer > Date: Sun, 3 Jul 2022 01:06:40 -0400 > Cc: Sean Whitton , Lars Ingebrigtsen , > Visuwesh , 56311@debbugs.gnu.org > > > > It's interesting to see commentary about how one shouldn't want to kill > buffers. There is a lot of functionality > > > revolving around killing buffers. > > > > Examples of such functionality? I'm not sure I understand what you > > have in mind here. > > I mean functions like kill-buffer, eww-buffer-kill,ido-kill-buffer, > project-kill-buffers, gnus-kill-buffer. There are many functions that > assist killing buffers. OK, and what is the relevance of that to the issue at hand? > > > I find that the more buffers I have open, the longer it takes to > > > find a given buffer. > > > > "Find" in what way? Please tell more about the problems you have in > > sessions with many buffers, because I'm not aware of any significant > > problems. > > When trying to switch to a buffer, the more buffers in the list, the more > work needs to be done to find the single buffer I do want. We have several features to make this easier. There's completion on buffer names, there's the "Buffers" menu on the menu bar, there are "C-x C-b" and electric-buffer-list -- and that's only in vanilla Emacs. > > > Personally, I never want to delete a file and keep the buffer around. > So I have replaced *all* my usages of > > > `delete-file` with this new one. > > > > That's fine: Emacs is great because it lets you do that to fit your > > personal needs. No one here is saying that it's wrong for you to do > > that > > In this thread, there are messages like "..we generally don't care about > that (because it does no harm to have unused buffers)...", an argument to > not close the buffer (because it allowed them to resurrect mistakenly > deleted files), and "They shouldn't be using [this command] a lot...". Note the "in general" part. This doesn't contradict your own personal needs, if they are special ones. > > the discussion is whether doing so is TRT for many/most Emacs > > users (which could have different workflows). > > How would we know if proposed functionality *would* be used by enough > users? What is a threshhold for enough users to add a function? We usually judge that by the number of people who request a feature.