Re: tramp (2.0.25); saving remote buffer fails

[Kai Großjohann]

"Clemens Fischer" <address@hidden> writes:

> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
>   logand(nil 3072)
>   byte-code("

Could you produce another backtrace with more Lisp and less
bytecode?  The solution is to look below the bytecode to find the
function that was called, then to find the *.el file containing this
function, and to load that with M-x load-library RET.  Repeat if the
new backtrace still has bytecode.

Thanks!

kai

PS: Maybe the bug has nothing to do with Tramp.  But at least I can
have a closer look...
-- 
~/.signature is: umop ap!sdn    (Frank Nobis)