I haven't been following the discussion (so I may be out of line), but
I hope that the fix suggested below is one we'd proffer only to XEmacs
Beta developers/testers and not to ordinary users.
on 02/16/2008 07:29 AM Michael Sperber said the following:
Mike Kupfer <mike.kupfer(a)sun.com> writes:
> I'm currently (as I type this in) unable to visit a directory using
> dired. It complains "operation not supported" on some other directory
> that's totally unrelated to the one I want to visit. I enabled
> debug-on-error and got this backtrace:
> Debugger entered--Lisp error: (file-error "Finding truename"
"Operation not supported on transport endpoint"
> apply(file-truename "/net/sfwnv/export/nv/")
> dired-handler-fn(file-truename "/net/sfwnv/export/nv/")
> dired-find-buffer-nocreate("/export/kupfer/tonic/stevel/" nil)
> dired-internal-noselect("/export/kupfer/tonic/stevel/" nil)
> dired-noselect("/export/kupfer/tonic/stevel" nil)
> #<compiled-function (dirname &optional switches) "...(7)"
[switches dirname switch-to-buffer dired-noselect] 4
> /export/kupfer/tonic/stevel/ is the directory I want to visit.
> /net/sfwnv/export/nv/ is an NFS directory that I had tried to visit
> earlier in the day but couldn't (permissions problem).
> I haven't looked at the relevant dired code, but I'm hypothesizing that
> it's trying to reclaim resources associated with the directory I
> couldn't visit. The buffer for that directory has this text:
> ls: error reading directory /net/sfwnv/export/nv/.: Permission denied
> total 0
> Let's try killing that buffer... done. And now dired lets me visit
It's trying to see if it can re-use the earlier buffer for the new dired
command you're doing, and, in the process of that, tries to find the
truename of the directory of that earlier buffer. You can set
`find-file-compare-truenames' and `dired-find-file-compare-truenames' to
nil to prevent it from doing that.
Vladimir G. Ivanovic
XEmacs-Beta mailing list