From: Sean Whitton <spwhitton@spwhitton.name>
To: Eli Zaretskii <eliz@gnu.org>, Zachary Kanfer <zkanfer@gmail.com>
Cc: 56311@debbugs.gnu.org
Subject: bug#56311: [PATCH] new function: delete-visited-file
Date: Wed, 29 Jun 2022 22:49:47 -0700 [thread overview]
Message-ID: <87tu82bszo.fsf@athena.silentflame.com> (raw)
In-Reply-To: <83k08y67ml.fsf@gnu.org>
Hello,
On Thu 30 Jun 2022 at 08:30am +03, Eli Zaretskii wrote:
>> From: Zachary Kanfer <zkanfer@gmail.com>
>> Date: Thu, 30 Jun 2022 00:26:06 -0400
>>
>> +** New command 'delete-visited-file'.
>> +This command deletes the file visited by a buffer, then closes the
>> +buffer.
>
> "Close the buffer" is not our terminology, you won't find it in our
> documentation. We say "kill the buffer".
>
> I also think "delete-visited-file" is not the best name for the
> command, since it doesn't tell all the truth about what it does.
>
> Apart of that, I have no opinion about this proposal, although each
> time I see suggestions for features to kill unused buffers or see
> people who are worried about such buffers, I raise a brow: in Emacs,
> we generally don't care about that (because it does no harm to have
> unused buffers), and if someone's usage patterns are such that they
> tend to create _gobs_ of large buffers most of which quickly become
> unused, there's midnight.el to take care of that.
I don't care about the buffer being killed either, but there isn't
currently a quick way to delete the file the selected buffer is
visiting, you have to type/complete its name. It would be nice to have
that, which I think this command provides.
--
Sean Whitton
next prev parent reply other threads:[~2022-06-30 5:49 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tu82bszo.fsf@athena.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=56311@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).