Using rsync method and dired, I'm getting an error when I visit a file
with <RET>:

    Signaling: (wrong-type-argument stringp nil)
      file-symlink-p(nil)
      vc-find-file-hook()
      run-hooks(find-file-hooks)
      after-find-file(nil t)
      find-file-noselect-1(#<buffer mla-candidate-info.txt> 
"/r@rsync:[EMAIL PROTECTED]:/home2/s/swift/misc-text/mla-candidate-info.txt" nil 
nil "/r@rsync:[EMAIL PROTECTED]:/home2/s/swift/misc-text/mla-candidate-info.txt" 
(1366417 -1))
      
find-file-noselect("/r@rsync:[EMAIL PROTECTED]:/home2/s/swift/misc-text/mla-candidate-info.txt"
 nil nil nil)
      
find-file("/r@rsync:[EMAIL PROTECTED]:/home2/s/swift/misc-text/mla-candidate-info.txt")
      dired-advertised-find-file()
      call-interactively(dired-advertised-find-file)

The *Messages* buffer with verbosity at 10 looks like this:

    Fetching /r@rsync:[EMAIL PROTECTED]:/home2/s/swift/misc-text/cv.log to tmp 
file...
    Fetching /r@rsync:[EMAIL PROTECTED]:/home2/s/swift/misc-text/cv.log to tmp 
file...done
    Wrong type argument: stringp, nil

After this error, a buffer visiting the file actually exists, but you
are not switched to it.  Therefore, if you try again pressing <RET>,
the right thing happens.  If you kill that buffer and try again,
however, you go back to the beginning and get the error again.

Reply via email to