unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: backup method
Date: Sat, 29 Jan 2005 12:42:31 -0600 (CST)	[thread overview]
Message-ID: <200501291842.j0TIgVw09020@raven.dms.auburn.edu> (raw)
In-Reply-To: <20050129060851.GQ6167@boetes.org> (message from Han Boetes on Sat, 29 Jan 2005 07:08:29 +0100)

Han Boetes wrote:

   I do have one question left though: Is this patch sufficiently portable?

   Looking through files.el I found this description of what a
   temporary-file-directory looks like:

I am not _sure_, but I have the impression that `temporary-file-directory'
was exactly intended for portability reasons.  I believe that it was
intended to be the "normal" place for the OS to put temporary files.
You normally do not have to customize it because the code you quoted
normally gets it right.  If it gets it wrong, you have to customize it.

I have the impression that to get the portability you want, you would
need two new variables, that would do what I believe
`temporary-file-directory' and  `small-temporary-file-directory' are
actually intended to do, `system-temporary-file-directory' and
`system-small-temporary-file-directory'.  I do not really know whether
that would really be the correct solution.

Note that we are discussing whether or not to make backup files while
discussing a problem that has nothing at all to do with whether it is
useful or not to make backup files.  The only thing we are worried
about is whether the file should be copied or overwritten on save.
Some people _want_ and _expect_ Emacs to make backups in /temp/,
because they do make changes there that they might regret.  They then
try to use the backup file, which is not there.  I have seen "bug"
reports by people who where very inconvenienced by this (for them)
unexpected behavior.  "How come Emacs always makes backup files
_except_ when I really need them?".

Default Emacs is not an overwrite-on-save system and it is not a
copy-on-save system either.  By default, Emacs copies on save if and
only if a backup is made.  This links two unrelated questions, "Do I
need a copy in case I regret my edits" and "Does this file need to be
copied or overwritten on save".  Obviously, there are going to be
situations where this creates problems.

I believe that the correct solution in this particular case is to make
`normal-backup-enable-predicate' use a customizable list of
directories in which no backups are made, say `no-backup-directories'.
We could then tell people that if they want remove "/temp/" or
equivalent from the list, they should set `backup-by-copying' to t, or
we could use a second customizable variable
`backup-by-copying-directories', to unlink the two problems (at least
in this particular case).

Sincerely,

Luc.

  reply	other threads:[~2005-01-29 18:42 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-27  0:02 backup method Han Boetes
2005-01-27  0:45 ` Luc Teirlinck
2005-01-27  1:20   ` Miles Bader
2005-01-27  1:37     ` Luc Teirlinck
2005-01-27  1:54     ` Han Boetes
2005-01-27 22:18       ` Richard Stallman
2005-01-28  3:56         ` Han Boetes
2005-01-29  4:16           ` Richard Stallman
2005-01-29  6:08             ` Han Boetes
2005-01-29 18:42               ` Luc Teirlinck [this message]
2005-01-29 21:06                 ` Stefan Monnier
2005-01-29 21:48                   ` Luc Teirlinck
2005-01-29 22:37                     ` Luc Teirlinck
2005-01-29 22:49                     ` Luc Teirlinck
2005-01-29 21:57                   ` Luc Teirlinck
2005-01-29 22:05                   ` Luc Teirlinck
2005-01-29 22:52                 ` Han Boetes
2005-01-29 23:50                   ` Stefan Monnier
2005-01-30 21:52                     ` Han Boetes
2005-01-31  0:20                     ` Richard Stallman
2005-01-31  0:57                       ` Stefan Monnier
2005-02-01 13:30                         ` Richard Stallman
2005-02-01 14:09                           ` Stefan Monnier
2005-02-03  6:40                             ` Richard Stallman
2005-02-03  9:27                               ` David Kastrup
2005-02-03 10:15                                 ` Han Boetes
2005-02-05  5:28                                 ` Richard Stallman
2005-02-05 10:26                                   ` David Kastrup
2005-02-06 10:29                                     ` Richard Stallman
2005-01-31  0:20                 ` Richard Stallman
2005-01-31  4:07                   ` Han Boetes
2005-01-29 20:06               ` Luc Teirlinck
2005-01-30 10:57               ` Richard Stallman
2005-01-30 11:39                 ` Han Boetes
2005-01-27 18:25   ` Kevin Rodgers
2005-01-27 20:25     ` Reiner Steib
2005-01-27 23:19       ` Miles Bader
2005-01-27 23:12     ` Miles Bader
2005-01-28  3:55     ` Richard Stallman
2005-01-27  1:47 ` Luc Teirlinck
2005-01-27  2:08   ` Han Boetes
2005-01-27  2:27     ` Han Boetes
2005-01-27  4:59       ` Han Boetes
2005-01-27  2:37     ` Miles Bader
2005-01-27  3:27       ` Han Boetes
2005-01-27  5:08 ` Eli Zaretskii
2005-01-27  5:27   ` Han Boetes
2005-01-27 19:41     ` Eli Zaretskii
2005-01-28  4:14       ` Han Boetes
2005-01-27  8:30   ` Kim F. Storm
2005-01-27 19:55     ` Luc Teirlinck
2005-01-27 21:12       ` Luc Teirlinck
2005-01-27 20:15     ` Luc Teirlinck
2005-01-27 22:19     ` Richard Stallman

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=200501291842.j0TIgVw09020@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --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 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).