From: Richard Stallman <rms@gnu.org>
To: James Ipswich <james.ipswich@proton.me>
Cc: emacs-devel@gnu.org
Subject: Re: Reconsider make-backup-files default value
Date: Tue, 17 Sep 2024 23:51:57 -0400 [thread overview]
Message-ID: <E1sqljR-0005w5-2f@fencepost.gnu.org> (raw)
In-Reply-To: <hRb-9aA6UUrj2IxA8n2asx770Cz8wnnxNY5dS4Y-n-v7tyLcjAdNE_eGClz-1miEh-l1_fB-6pioYj-chqoh2w2sypMMQ3hqltxPGntbVDs=@proton.me> (message from James Ipswich on Sun, 15 Sep 2024 22:19:42 +0000)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> Emacs has traditionally kept all defaults very minimal, and most
> functionality needs to be explicitly enabled by the user. For example,
> out of the box minibuffer and CAPF completion is quite plain.
This is not a rule, just a usual approach. It tends to keep
the default mode of operation simple. If a feature is a possible
convenience, people can turn it on if they want it.
> However, make-backup-files default value is t, which I think goes
> against this philosophy.
That is very important. If you don't save the previous version, you
will regret it. Being safe is a better default than being risky.
Thus, whether to enable an option by default is a matter of what it does.
Lets not make rigidity our rigid principle.
Changes in the details of making or naming backups are a different
issue. They are not risky as disabling backups would be.
If we want to introduce a method that is not currently an option,
we should introduce it as an option.
Changing the default details of making or naming backups is
possible too, but we shouldn't consider changing to a method
until it has been in a release for a year and we can see how
much people like it.
"Hiding" backup files might cause a risk that other changed details
would not cause. If you are not an expert on Emacs, and you don't see
a backup file when you list that directory, you may not realize that
it exists. You might think that the old version is lost, when in fact
you have it in a backup file.
The harm done by one instance of that could easily outweigh a thousand
instances of being annoyed about "clutter".
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2024-09-18 3:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 22:19 Reconsider make-backup-files default value James Ipswich
2024-09-15 23:29 ` Jeremy Baxter
2024-09-16 12:04 ` Eli Zaretskii
2024-09-18 20:14 ` Petteri Hintsanen
2024-09-18 21:46 ` Christopher Howard
2024-09-19 5:23 ` Eli Zaretskii
2024-09-19 6:10 ` Juri Linkov
2024-09-19 6:36 ` Eli Zaretskii
2024-09-15 23:40 ` pinmacs
2024-09-16 12:10 ` Eli Zaretskii
2024-09-16 0:03 ` James Ipswich
2024-09-16 0:14 ` Jeremy Baxter
2024-09-16 12:02 ` Eli Zaretskii
2024-09-18 13:24 ` Po Lu
2024-09-18 13:37 ` Emanuel Berg
2024-09-18 23:31 ` Stefan Kangas
2024-09-19 2:41 ` Po Lu
2024-09-19 5:23 ` Alfred M. Szmidt
2024-09-20 8:23 ` Andrea Corallo
2024-09-19 5:49 ` Eli Zaretskii
2024-09-18 3:51 ` Richard Stallman [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-16 0:15 Martin Edström
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=E1sqljR-0005w5-2f@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=james.ipswich@proton.me \
/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.