Re: Find-file problem when connecting from Windows box with plink

[Michael Albinus]

Jyrki Jaakkola <address@hidden> writes:

Thanks for the debug buffer. Unfortunately, there's nothing special,
everything looks like it should.

> backtrace:
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>   intern(nil [0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0])
>   vc-file-clearprops(nil)
>   vc-file-not-found-hook()

Hmm. nil in vc-file-clearprops means, that buffer-file-name is nil.

You've said in your first message, that opening the file from
somewhere works. But then you've opened a special buffer for showing
files, and selected the file for opening there. Could you, please,
describe exactly which steps you have performed?

>   run-hook-with-args-until-success(vc-file-not-found-hook)
>   byte-code("unreadable" [filename buf error file-exists-p 
> file-readable-p kill-buffer signal file-error "File is not readable"
> run-hook-with-args-until-success find-file-not-found-hooks t] 4)
>   find-file-noselect-1(#<buffer +lisp-server.lisp>
> "/plink:address@hidden:/home/foo/+lisp-server.lisp" nil nil
> "/plink:address@hidden:/home/foo/+lisp-server.lisp" (149209 (-1
> 0)))

Marking "/plink:address@hidden:/home/foo/+lisp-server.lisp" as
unreadable looks strange. According to your traces, this file is
readable:

> 15:27:13 tramp-send-command (6) # test -r /home/foo/\+lisp-server.lisp 
> 2>/dev/null; echo tramp_exit_status $?
> 15:27:13 tramp-wait-for-regexp (6) #
> tramp_exit_status 0
>
> ///13c31611a4ffe3666f491badeda158fc

Somehow, I need a scenario for reproduction :-(

Best regards, Michael.