Re: Bug in remote file save.

[Alan Shutko]

>     I dired a directory remotely, C-xd
>     /address@hidden:/var/www/html/website, open and edit a file, it saves
>     the first time correctly.  For each further edit, it gives a
>     beep and the message "Keyboard macro terminated by command
>     ringing the bell".

Could you compare the time on your computer with the time on the
remote host?  Or, immediately after you save a file, look at it in
dired to see the timestamp?

I think I've seen things like this when the clock on the remote host
was significantly ahead of my time (by several minutes).  When I try
to save, I get a backtrace somewhat like this (sorry, this is from
21.2, since that's the only machine with access to a misconfigured
clock right now... I'll try a better backtrace when I get to work).

I don't know why it complains about a keyboard macro, but it does.

Debugger entered--Lisp error: (error "Keyboard macro terminated by a command ri$
  beep()
  byte-code("address@hidden    !\"\210Ê^ZË )address@hidden@Í^KÎ\$
  ask-user-about-supersession-threat("/tsreast:/user2/intouch/atstest")
  set-buffer-modified-p(t)
  byte-code("^H^Q\n^SÅ\f!\207" [last-coding-system-used coding-system-used file$
  ange-ftp-write-region(1 18 "/tsreast:/user2/intouch/atstest" nil t)
  apply(ange-ftp-write-region (1 18 "/tsreast:/user2/intouch/atstest" nil t))
  ange-ftp-hook-function(write-region 1 18 "/tsreast:/user2/intouch/atstest" ni$
  write-region(1 18 "/tsreast:/user2/intouch/atstest" nil t "/tsreast:/user2/in$
  basic-save-buffer-2()
  basic-save-buffer-1()
  basic-save-buffer()
  save-buffer(1)
* call-interactively(save-buffer)

-- 
Alan Shutko <address@hidden> - In a variety of flavors!
I sold my sole to Satan. He's been floundering around ever since.