Re: convince NTemacs it _can_ symlink

[Tom_Roche]

I wrote:
>>> [when in tramp, and] I try to symlink, NTemacs becomes confused:

>>>> Symbol's function definition is void: make-symbolic-link

>>> presumably because it knows it can't do this ... on _its_
>>> filesystem.

On 18 Mar 2001, Andrew Innes wrote:
>> It probably makes sense for all file functions that can invoke
>> handlers to always be defined, even if they have to throw an error
>> on platforms where the functionality cannot be supported natively,
>> so that remote file system packages like tramp and ange-ftp can
>> still work.

Eli Zaretskii <eliz@is.elta.co.il> Mon, 19 Mar 2001 09:27:53 +0200
<rearranged>
> In my experience, this approach usually opens a Pandora box: some
> packages test for make-symbolic-link being fboundp to decide whether
> the platform supports symlinks.

> Windows isn't Unix, even if tramp wants us to believe it is ;-)

But the point of tramp is to make the 'platform' (the local host) less
relevant (if not irrelevant). Why should it matter what Windows can or
can't do, as long as it can run a session on a remote host?

FWIW, Tom_Roche@ncsu.edu