From: Christopher Howard <christopher@librehacker.com>
To: Petteri Hintsanen <petterih@iki.fi>
Cc: Eli Zaretskii <eliz@gnu.org>, Jeremy Baxter <jeremy@baxters.nz>,
james.ipswich@proton.me, emacs-devel@gnu.org
Subject: Re: Reconsider make-backup-files default value
Date: Wed, 18 Sep 2024 13:46:18 -0800 [thread overview]
Message-ID: <87frpwprdh.fsf@librehacker.com> (raw)
In-Reply-To: <x2mikusu3bc.fsf@iki.fi> (Petteri Hintsanen's message of "Wed, 18 Sep 2024 23:14:47 +0300")
I would vote for keeping backups turned on by default.
Something I have wondered about for a while is why the kept-old-versions default is 2 instead of 1. It makes sense of course that you would want to keep, e.g., the original (template) version of a config file, but what is special about the first revision you made to it?
When using Emacs' backup system, which I sometimes find useful, I usually increase kept-new-versions to 10, though I suppose 2 makes a more sensible default.
--
Christopher Howard
next prev parent reply other threads:[~2024-09-18 21:46 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 [this message]
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=87frpwprdh.fsf@librehacker.com \
--to=christopher@librehacker.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=james.ipswich@proton.me \
--cc=jeremy@baxters.nz \
--cc=petterih@iki.fi \
/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).