From: Chong Yidong <cyd@stupidchicken.com>
To: "Ramkumar R. Aiyengar" <andyetitmoves@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: 23.0.60; find-backup-file-name assumes base name of backup file names
Date: Mon, 07 Apr 2008 11:18:25 -0400 [thread overview]
Message-ID: <87lk3phewu.fsf@stupidchicken.com> (raw)
> make-backup-file-name-function is a customizable variable in files.el
> for deciding the backup file name for a file. find-backup-file-name
> uses make-backup-file-name-1 for finding out the base names of the
> backup files:
>
> (let* ((basic-name (make-backup-file-name-1 fn))
> (base-versions (concat (file-name-nondirectory basic-name)
> ".~"))
>
> This assumes that make-backup-file-name is used for generating the
> backup file names, while make-backup-file-name-function could be
> customized. The result of this is, any customization to
> make-backup-file-name-function doesn't work as expected when the
> backup file name is in a different place than what is provided by the
> stock function (like say, a different directory).
In the code, find-backup-file-name only uses make-backup-file-name-1
when checking for numeric backup files (usually for files under version
control). If it determines that a non-numeric backup file is desired,
it calls make-backup-file-name, which correctly checks
make-backup-file-name-function as desired. Note that
make-backup-file-name-function only applies to non-numeric backup files.
So I think there is no problem here, unless you can give instructions
for reproducing a bug.
next reply other threads:[~2008-04-07 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 15:18 Chong Yidong [this message]
2008-04-07 15:33 ` 23.0.60; find-backup-file-name assumes base name of backup file names Ramkumar R. Aiyengar
2008-04-08 1:20 ` Chong Yidong
-- strict thread matches above, loose matches on Subject: below --
2008-03-22 2:27 Ramkumar R. Aiyengar
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=87lk3phewu.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=andyetitmoves@gmail.com \
--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 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.