From: Eli Zaretskii <eliz@gnu.org>
To: Zachary Kanfer <zkanfer@gmail.com>
Cc: larsi@gnus.org, visuweshm@gmail.com, 56311@debbugs.gnu.org,
spwhitton@spwhitton.name
Subject: bug#56311: [PATCH] new function: delete-visited-file
Date: Sun, 03 Jul 2022 09:04:31 +0300 [thread overview]
Message-ID: <83zghqag0g.fsf@gnu.org> (raw)
In-Reply-To: <CAFXT+RMrdxbzJE0Jeji6ZJ5uNoijH3BhciHwh9LE7U5fVfQSVw@mail.gmail.com> (message from Zachary Kanfer on Sun, 3 Jul 2022 01:06:40 -0400)
> From: Zachary Kanfer <zkanfer@gmail.com>
> Date: Sun, 3 Jul 2022 01:06:40 -0400
> Cc: Sean Whitton <spwhitton@spwhitton.name>, Lars Ingebrigtsen <larsi@gnus.org>,
> Visuwesh <visuweshm@gmail.com>, 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.
next prev parent reply other threads:[~2022-07-03 6:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 4:26 bug#56311: [PATCH] new function: delete-visited-file Zachary Kanfer
2022-06-30 5:30 ` Eli Zaretskii
2022-06-30 5:49 ` Sean Whitton
2022-06-30 5:56 ` Eli Zaretskii
2022-06-30 6:20 ` Visuwesh
2022-06-30 10:27 ` Lars Ingebrigtsen
2022-06-30 16:29 ` Sean Whitton
2022-07-01 3:29 ` Zachary Kanfer
2022-07-01 5:57 ` Eli Zaretskii
2022-07-03 5:06 ` Zachary Kanfer
2022-07-03 6:04 ` Eli Zaretskii [this message]
2022-08-02 11:12 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83zghqag0g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56311@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=spwhitton@spwhitton.name \
--cc=visuweshm@gmail.com \
--cc=zkanfer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.