Romain Francoise wrote:

Nope, and starting Emacs with -Q disables all customizations.

I know, I just wanted to make sure that you really started with -Q. :-)

Which filesystem are you using?  Is it a regular filesystem, or a remote
NFS mount (or something similar)?

A normal local file system on hard disk, type ext3, mounted with nosuid and
nodev options on /home.

Can you please do "M-x debug-on-entry rename-file" and tell me if and
when this pops up the debugger in our scenario?


Never.

That confirms that for you Emacs does not try to make a backup, consistent
with the previous observations.  Contrast this with what I get when I type
C-x C-s:

Debugger entered--entering a function:
* rename-file("/home/sven/bar" "/home/sven/bar~" t)
  byte-code([snipped])
  byte-code([snipped])
  backup-buffer()
  basic-save-buffer-2()
  basic-save-buffer-1()
  basic-save-buffer()
  save-buffer(1)
  call-interactively(save-buffer)

Typing "c" in the debugger changes the first line to

Debugger entered--returning value: nil

Typing "c" again pops up the *Warning* buffer, typing "C-g" enters the
debugger again:

Debugger entered--entering a function:
* rename-file("/home/sven/bar~" "/home/sven/bar")
  byte-code("[snip]" [setmodes success buffer-file-name rename-file] 3)
  read-coding-system("Select coding system (default compound-text): " 
compound-text)
  select-safe-coding-system-interactively(1 1967 (x-ctext [snipped] ) 
(undecided-unix iso-latin-1) nil compound-text)
  select-safe-coding-system(1 1967 undecided-unix nil "/home/sven/bar")
  write-region(1 1967 "/home/sven/bar" nil t "~/bar")
  basic-save-buffer-2()
  basic-save-buffer-1()
  basic-save-buffer()
  save-buffer(1)
  call-interactively(save-buffer)

in accordance to what I observed earlier.

Typing "c" in the debugger changes the first line again to

Debugger entered--returning value: nil

and another "c" finally gets me out of the debugger.


Just now I notice something I did not spot earlier: You did not
accidentally try this in a temporary directory where Emacs does not make
backups at all, as the manual states in section 23.3.2?

,----
|    The default value of the `backup-enable-predicate' variable prevents
| backup files being written for files in the directories used for
| temporary files, specified by `temporary-file-directory' or
| `small-temporary-file-directory'.
`----

If you had done that, our discrepancies could be explained. :-)
If not, I'm at my wits end and we probably need third-party help.

Cheers,

Sven







--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to