Daniel Pittman writes:
> On Fri, 29 Oct 1999, Pete Forman <[EMAIL PROTECTED]>
> wrote:
>
> > Daniel Pittman writes:
> > > > Okay, I've got 1.180 now. The problem remains. Here is another
> > > > backtrace. I am unable to spot the linkage from expand-file-name
> > > > to efs-host-type.
> > >
> > > That's very odd. Can you try, painful as it is, putting a
> > > breakpoint in 'rcp-file-name-handler' and step through the code to
> > > see where it goes wrong?
> >
> > I'd done that. It is fine. It is not called by the following though.
> >
> > (expand-file-name "/r:morse:.vm")
>
> Hmmm. That *should* be called. 'find-file-name-handler' should
> match the path and return a result.
find-file-name-handler does work properly, returning
rcp-file-name-handler or efs-file-handler-function as appropriate.
> With XEmacs 20.4 I get:
> (expand-file-name "/r:melancholia:.vm")
> "/r@scp:daniel@melancholia:/home/daniel/.vm"
>
> Something is not right in there at a higher level than RCP then. All I
> can think of is that for some strange reason the variable
> 'rcp-file-name-handler-alist' has the wrong value on your system or
> something.
All the associated values in that alist are rcp-handle-*.
> > > RCP *should* handle both 'find-file' and 'expand-file-name'
> > > internally, not calling the file handler stuff at all, I think.
> >
> > expand-file-name is a built-in function.
>
> 'find-file-name-handler' should match the rcp handler and pass the
> request to 'rcp-file-name-handler' which should in turn call
> 'rcp-handle-expand-file-name'.
rcp-file-name-handler is called from read-file-name ... substitute-in-
file-name. It is not called from the first line of find-file-noselect,
which calls expand-file-name.
BTW, I have taken to running XEmacs under dbx (on Solaris) to chase
this. Can anyone give me a hint as to how to print out lisp objects,
especially strings.
--
Pete Forman
Western Geophysical
[EMAIL PROTECTED]
