Actually, there was a stupid bug in my code where set-file-modes
was returning the integer return status of the `chmod' rather
than throwing an error if the chmod failed.
In the mean time, I've implemented file-ownership-preserved-p and
cleaned up my current "new VC" patch a little.
Also, I've
Using a chain like
/r@multiu:ssh#[EMAIL PROTECTED]:ssh#[EMAIL PROTECTED]:/path/to/file,
works fine except for one thing: the permissions of the file are not
preserved as they are normally.
Mark.
I was looking at rcp-handle-file-attributes trying to see how to
(mis)use Perl into giving us the mtime information and while
doing it, I noticed that we currently use `ls -iLldn' which means
that in case of a symlink, we get the data of what is pointed by the
symlink rather than the data of the
> "KG" == Kai Großjohann <[EMAIL PROTECTED]> writes:
KG> Could you try executing write-region to write to a remote file
KG> and check if that changes the permissions?
It didn't change the permissions.
Mark.
[EMAIL PROTECTED] (Mark A. Hershberger) writes:
> Using a chain [...] the permissions of the file are not preserved as
> they are normally.
I think the permissions get hosed in all inline methods. Must do
something about this. Hm. But I don't know why this happens!
rcp.el sends the following
"Stefan Monnier" <[EMAIL PROTECTED]> writes:
> BTW, does any one have a clue as to why I sometimes get errors
> where zerop is applied to the symbol `hello' (typically returned
> from rcp-run-test) ?
This is a timing problem. Oh, those thorny timing problems :-(
rcp.el used to send `echo hello'
[EMAIL PROTECTED] (Mark A. Hershberger) writes:
> > "KG" == Kai Großjohann <[EMAIL PROTECTED]> writes:
>
> KG> Could you try executing write-region to write to a remote file
> KG> and check if that changes the permissions?
>
> It didn't change the permissions.
Err. So what is save
Excerpts from mail: (25-Apr-2000) Re: Shell by Kai Grossjohann
>> Good reasons, but WIBNI there was a `rcp-open-connection-ssh' which
>> *did* do a "ssh -l user host /bin/sh" to avoid .login problems?
>> There's no reason to cripple ssh support like this just because the
>> other methods can't han
> PS: I still don't have access to the new VC, so I can't really test
> things. But I suppose I could integrate your changes to see if
> they still work on the old VC...
Now that I think about it, my changes in the VC "advices" will only
work properly with the old VC if vc.el is loaded b
"Edward J. Sabol" <[EMAIL PROTECTED]> writes:
> Good reasons, but WIBNI there was a `rcp-open-connection-ssh' which
> *did* do a "ssh -l user host /bin/sh" to avoid .login problems?
> There's no reason to cripple ssh support like this just because the
> other methods can't handle it.
Could you m
10 matches
Mail list logo
