From: Kaushal Modi <kaushal.modi@gmail.com>
To: 22625@debbugs.gnu.org
Subject: bug#22625: 24.5; Please add index entry for `~ filename suffix' to manual for node `Backup Names'
Date: Sat, 13 Feb 2016 10:24:56 -0500 [thread overview]
Message-ID: <CAFyQvY0XjiabAOQF4CBrjaMXFApxsfvPURtjSQK_9h0NBQvLkw@mail.gmail.com> (raw)
In-Reply-To: <86d0f742-1666-4da5-9192-eb505dd493f3@default>
[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]
I am not sure I understood the request.
On emacs built from emacs-25 branch (could not verify the same on 24.5), by
doing,
C-h i g (emacs) Backup Names
I get a very good explanation of how the backup files are named.
=====
When Emacs makes a backup file, its name is normally constructed by
appending ‘~’ to the file name being edited; thus, the backup file for
‘eval.c’ would be ‘eval.c~’.
If access control stops Emacs from writing backup files under the
usual names, it writes the backup file as ‘~/.emacs.d/%backup%~’. Only
one such file can exist, so only the most recently made such backup is
available.
Emacs can also make "numbered backup files". Numbered backup file
names contain ‘.~’, the number, and another ‘~’ after the original file
name. Thus, the backup files of ‘eval.c’ would be called ‘eval.c.~1~’,
‘eval.c.~2~’, and so on, all the way through names like ‘eval.c.~259~’
and beyond.
[snip]
=====
Should this bug be closed?
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1514 bytes --]
next prev parent reply other threads:[~2016-02-13 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 23:04 bug#22625: 24.5; Please add index entry for `~ filename suffix' to manual for node `Backup Names' Drew Adams
2016-02-13 13:39 ` Eli Zaretskii
2016-02-13 15:24 ` Kaushal Modi [this message]
2016-02-13 15:37 ` Eli Zaretskii
2016-02-13 15:56 ` Eli Zaretskii
[not found] <<86d0f742-1666-4da5-9192-eb505dd493f3@default>
[not found] ` <<83r3gg6867.fsf@gnu.org>
2016-02-13 16:58 ` Drew Adams
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=CAFyQvY0XjiabAOQF4CBrjaMXFApxsfvPURtjSQK_9h0NBQvLkw@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=22625@debbugs.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 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.