From: Skip Montanaro <skip.montanaro@gmail.com>
To: tomas@tuxteam.de
Cc: Help GNU Emacs <help-gnu-emacs@gnu.org>, tom@wallenfang.de
Subject: Re: How to disable auto save on Emacs 26.1
Date: Thu, 4 Oct 2018 07:55:45 -0500 [thread overview]
Message-ID: <CANc-5UzvdQAx1YJH94DqJ4QvMjU0OvUfp5_ap9GZWujTCNOXAQ@mail.gmail.com> (raw)
In-Reply-To: <20181004110446.GA31656@tuxteam.de>
> If your concern is file system clutter, better leave auto-save alone.
> It's not going to clutter your file system (unless something else is
> going horribly wrong). As for backup, you can disable it or even teach
> it to use one directory for all backups (I have typically something
> beneath my ~/.emacs.d).
Coming a bit late to the game... Adding to Tomás's point, if you want
to eliminate backup files, don't just disable it. Replace it with a
proper version control system of some sort. Think of backup files (I
generally use numeric backups to actually retain more than one old
copy - more clutter!) as a defense against shooting yourself in the
foot. A version control system does that, only better. Tools like Git
or Mercurial make it trivial to create and manage little repositories
("git init" creates a new repo in the current directory, for example).
You need not push changes to a central server if you don't care to.
The elements in the filesystem which support the repository will
generally be invisible to the casual glance (hiding as directories
with leading dots on Unix-type systems). Most are well-integrated with
Emacs, so you can manage commits and other activities directly from
within Emacs (I use the vc package). Furthermore, once Emacs knows a
version control system has your back, it stops saving those
(pesky-to-you) backup files.
I apologize if this is all old hat. I wanted to make sure you
understood that backup files serve a valuable purpose (as do their big
brethren, version control systems). I suspect most folks reading this
mailing list have been thankful for this feature on more than one
occasion.
Skip
next prev parent reply other threads:[~2018-10-04 12:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 13:10 How to disable auto save on Emacs 26.1 Tom Wallenfang
2018-10-03 13:34 ` Martin Šlouf
2018-10-03 13:55 ` Stefan Monnier
[not found] ` <mailman.1669.1538575056.1284.help-gnu-emacs@gnu.org>
2018-10-03 14:16 ` Tom Wallenfang
2018-10-04 11:04 ` tomas
2018-10-04 12:55 ` Skip Montanaro [this message]
2018-10-04 14:47 ` Van L
2018-10-06 11:34 ` Fossil [Was: Re: How to disable auto save on Emacs 26.1] Garreau, Alexandre
2018-10-06 14:32 ` Van L
2018-10-06 19:17 ` tomas
2018-10-04 17:21 ` How to disable auto save on Emacs 26.1 Marcin Borkowski
2018-10-06 6:24 ` Marcin Borkowski
[not found] ` <mailman.1701.1538657386.1284.help-gnu-emacs@gnu.org>
2018-10-05 18:04 ` James K. Lowden
[not found] ` <mailman.1698.1538651613.1284.help-gnu-emacs@gnu.org>
2018-10-04 13:10 ` Stefan Monnier
2018-10-04 14:49 ` tomas
2018-10-04 13:44 ` Tom Wallenfang
[not found] ` <mailman.1668.1538573687.1284.help-gnu-emacs@gnu.org>
2018-10-03 14:19 ` Tom Wallenfang
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=CANc-5UzvdQAx1YJH94DqJ4QvMjU0OvUfp5_ap9GZWujTCNOXAQ@mail.gmail.com \
--to=skip.montanaro@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tom@wallenfang.de \
--cc=tomas@tuxteam.de \
/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.
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).