all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Visuwesh <visuweshm@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Zachary Kanfer <zkanfer@gmail.com>, 56311@debbugs.gnu.org
Subject: bug#56311: [PATCH] new function: delete-visited-file
Date: Thu, 30 Jun 2022 11:50:50 +0530	[thread overview]
Message-ID: <87wncyr7st.fsf@gmail.com> (raw)
In-Reply-To: <83k08y67ml.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 30 Jun 2022 08:30:10 +0300")

[வியாழன் ஜூன் 30, 2022] Eli Zaretskii wrote:

> 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.

FWIW, the fact that Emacs leaves the buffer around has saved my back at
least twice,

    . when I accidentally deleted the wrong files in dired due to
      stale marks.
    . when I tried to fix a broken symlink but got the argument order in
      ln wrong and had the real file "zeroed".






  parent reply	other threads:[~2022-06-30  6:20 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wncyr7st.fsf@gmail.com \
    --to=visuweshm@gmail.com \
    --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 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.