Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zftp annoyance
- X-seq: zsh-workers 14471
- From: Peter Stephenson <pws@xxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: zftp annoyance
- Date: Thu, 24 May 2001 15:31:07 +0100
- In-reply-to: "Oliver Kiddle"'s message of "Thu, 24 May 2001 15:08:47 BST." <3B0D15EF.AF9935D5@xxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
Oliver Kiddle wrote:
> I'm using zftp to transfer things back and forth from a server.
> Unfortunately, every time the connection times out and zftp reconnects
> the transfer type is reverting to ASCII. Surely it ought to be restoring
> the transfer type when it reconnects?
>
> This may just be something related to the particular ftp server - I
> normally use ncftp because I would normally get one file and quit so I'm
> not hugely familiar with zftp. Is it possible to make binary the default
> transfer type for zftp?
The zftp core code will switch to binary if the remote server claims to be
UNIX with 8-bit characters. (Actually it won't do this until you are
logged in, because some servers won't let you, but this shouldn't be a
problem.)
Look and see if $ZFTP_SYSTEM contains "UNIX Type: L8"; if not, it won't
happen automatically.
It should be easy to adapt the function suite to remember this. It would
be even easier to make binary the default: just doctor zfopen and zfanon
and put `zftype binary' at the end. Hooks aren't currently implemented,
but that could be done.
Making zfget support [user@]host:file and URL notation for one-off
retrievals is another useful, and relatively simple, possibility. I
haven't been doing much with zftp recently.
My own bugbear is that interrupt handling is very bad. I was hoping
someone else would get fed up with this and fix it.
--
Peter Stephenson <pws@xxxxxxx> Software Engineer
CSR Ltd., Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070
**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential
and/or privileged material.
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is
prohibited.
If you received this in error, please contact the sender and
delete the material from any computer.
**********************************************************************
Messages sorted by:
Reverse Date,
Date,
Thread,
Author