Message-ID: <[EMAIL PROTECTED]>
Priority: NORMAL
X-Mailer: Execmail for Win32 5.1 Build (9)
MIME-Version: 1.0
Content-Type: Text/Plain; CHARSET="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
On Sun, 05 Dec 1999 13:45:05 -0500 Jeffrey Juliano <[EMAIL PROTECTED]>=20
wrote:
> On 11/1/99, Kai Gro=DFjohann wrote:
> >=20
> > Jeffrey Juliano <[EMAIL PROTECTED]> writes:
> >=20
> > > I think the problem lies in a text/binary mode thing. ssh requires
I wasn't reading the list on 11/1/99, so forgive me if this is=20
revisiting old ground. But I'm having a similar kind of problem with=20
scp. If I "get" a text file from a remote Unix to a local NT with scp=20
(not using rcp.el or emacs or anything else), the file gets truncated=20
precisely as if I had transferred it using ftp in BINARY mode rather=20
than ASCII (ftp in ASCII mode transfers it OK).
Has anyone sorted out this problem already? (If I have to do it=20
myself, I'm inclined to leave the specification of the standard scp=20
unchanged, but to produce a variant, say scp_a, to do transfers in text
mode, and have rcp.el choose which one to use, perhaps a la ange-ftp. =20
The variant would have to be available on both machines involved.)
joe stoy
