Re: tramp (2.0.25); saving remote buffer fails

[Kai Großjohann]

"Clemens Fischer" <address@hidden> writes:

> i had edited a file remotely via ange-ftp (i hope you are indeed
> responsible for the bug and their reports :), and after having
> finished the edit of just three lines, i hit C-x C-s to save them:
>
> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
>   logand(nil 3072)
>   byte-code("
> 
> 
>   byte-code("
> 
> 
>   backup-buffer()
>   basic-save-buffer-2()
>   basic-save-buffer-1()
>   basic-save-buffer()
>   save-buffer(1)
>   call-interactively(save-buffer)
>
> i don't know if this can be reliably reproduced, at least i didn't
> manage to get the file saved.  interestingly enough, after logging in
> the second time, the file seemed to have incorporated the changes
> fine.
>
> the course of action was this:
>
> - C-x C-f /address@hidden:/
> - <password>
> - up comes dired
> - navigate to the file in question,
> - open it,
> - edit it,
> - save it (BBBOOOOOOMMM)!
> - setting debugging etc, and there you have it.

Your default method is ssh, therefore /address@hidden:/ should have
invoked Tramp with the ssh method.

Is this the case?

What happens with /ftp:address@hidden:/ instead of /address@hidden:/?

Sorry it took me so long to respond.

-- 
~/.signature is: umop ap!sdn    (Frank Nobis)