From: James Ipswich <james.ipswich@proton.me>
To: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Reconsider make-backup-files default value
Date: Sun, 15 Sep 2024 22:19:42 +0000 [thread overview]
Message-ID: <hRb-9aA6UUrj2IxA8n2asx770Cz8wnnxNY5dS4Y-n-v7tyLcjAdNE_eGClz-1miEh-l1_fB-6pioYj-chqoh2w2sypMMQ3hqltxPGntbVDs=@proton.me> (raw)
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.
However, make-backup-files default value is t, which I think goes
against this philosophy. If I open stock Emacs, with no configuration,
it pollutes all directories with backup files whenever I edit something.
This is a bit intrusive as I have never enabled such a functionality.
I understand this default is old, and comes from a time when machines
were less reliable and version control systems were not widely used. I
also understand some current users enjoy this functionality as an extra
safety net.
Personally, I think make-backup-files should default to nil or some
other less intrusive configuration, which would be better aligned with
the rest of Emacs defaults and how other software behaves.
Any thoughts?
next reply other threads:[~2024-09-15 22:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 22:19 James Ipswich [this message]
2024-09-15 23:29 ` Reconsider make-backup-files default value 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
-- 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
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='hRb-9aA6UUrj2IxA8n2asx770Cz8wnnxNY5dS4Y-n-v7tyLcjAdNE_eGClz-1miEh-l1_fB-6pioYj-chqoh2w2sypMMQ3hqltxPGntbVDs=@proton.me' \
--to=james.ipswich@proton.me \
--cc=emacs-devel@gnu.org \
/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).