zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Non-patch for zftp
Date: Sat, 20 Feb 1999 16:41:27 +0100	[thread overview]
Message-ID: <9902201541.AA37470@ibmth.df.unipi.it> (raw)

I've made some changes to zftp; since it applies to pws-8 and I'm about to
produce pws-9, it seems pointless to post it separately, but here is a list
of changes that will appear.

1. The functions in Misc/zftp-functions now avoid using zftp in subshells,
since I discovered that on Irix 6.2 it doesn't work --- the control fd is
invalid after a fork().  That's strange, since I vaguely thought I'd
originally tried it there and it did work.  However, I haven't been able to
track down any change which has affected this.  It's OK on every other OS
I've tested (the Linux box is currently down).

2. The zf* functions now have auto-open capability:  if the connection
times out, `zftp test' should be able to spot this and the functions will
transparently re-open the connection --- assuming you set it up in the
usual way with zfopen.  Also, if you explicitly close the connection, a
zfcd or zfdir will re-open it permanently while zfget will open it just for
that file grab (etc.).

3. There are more `return 6' statements in the source; 6 is the special
code for `don't even think about doing anything else', so this ought to
reduce the incidence of multiple error messages.

4. New Functions/Completion/_zftp:  currently this uses the old-style
completion functions zfget_match and zfcd_match, but it could be made
smarter.  (For example, prefix handling of directories can now be done as
if they were real directories.)

-- 
Peter Stephenson <pws@ibmth.df.unipi.it>       Tel: +39 050 844536
WWW:  http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy


                 reply	other threads:[~1999-02-20 16:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9902201541.AA37470@ibmth.df.unipi.it \
    --to=pws@ibmth.df.unipi.it \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).