If you choose to have a single backup file (this is the default), the backup file's name is constructed by appending `~' to the file name being edited; thus, the backup file for `eval.c' would be `eval.c~'.
If you choose to have a series of numbered backup files, backup file names are made by appending `.~', the number, and another `~' to the original file name. Thus, the backup files of `eval.c' would be called `eval.c.~1~', `eval.c.~2~', and so on, through names like `eval.c.~259~' and beyond.
If protection stops you from writing backup files under the usual names, the backup file is written as `%backup%~' in your home directory. Only one such file can exist, so only the most recently made such backup is available.
The choice of single backup or numbered backups is controlled by the
variable version-control
. Its possible values are
t
nil
never
You can set version-control
locally in an individual buffer to
control the making of backups for that buffer's file. For example,
Rmail mode locally sets version-control
to never
to make sure
that there is only one backup for an Rmail file. See section Local Variables.
If you set the environment variable VERSION_CONTROL
, to tell
various GNU utilities what to do with backup files, Emacs also obeys the
environment variable by setting the Lisp variable version-control
accordingly at startup. If the environment variable's value is `t'
or `numbered', then version-control
becomes t
; if the
value is `nil' or `existing', then version-control
becomes nil
; if it is `never' or `simple', then
version-control
becomes never
.
For files managed by a version control system (see section Version Control), the variable vc-make-backup-files
determines whether
to make backup files. By default, it is nil
, since backup files
are redundant when you store all the previous versions in a version
control system. See section VC Workfile Handling.
Go to the first, previous, next, last section, table of contents.