zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@cambridgesiliconradio.com>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: Proxy support for zftp functions
Date: Mon, 22 May 2000 17:17:23 +0100	[thread overview]
Message-ID: <0FUY009QZYKZGE@la-la.cambridgesiliconradio.com> (raw)
In-Reply-To: "Your message of Mon, 22 May 2000 20:03:46 +0400." <000d01bfc407$4f1c1980$21c9ca95@mow.siemens.ru>

> > This was on my original plan, but not only didn't I need it
> > myself I didn't
> > even have a proxy host to try on, so I never thought much about it.
> > I was actually imagining doing it in the C code.
> 
> Yes, it makes more sense. Proxy is relevant only for a logon - then it
> is completely transparent (hopefully :-).

Actually, for just that reason, your idea of doing it in the functions is
probably better.  The less hidden code the more I like it.

> Actually, much more interesting (needed) feature is ls parsing.
> Currently, zftp relies on MDTM/SIZE to exist - and, unfortunately, they
> are missing in "common" Unix servers. Have you ever thought about it?

There's a nice project for someone with a bit of time.  This can probably
be done in shell functions too --- it's system-specific, so not good to
hard code, and the only place this is used internally is for supplying to
functions doing progress reports, which can be rewritten to use information
returned by ls where necessary.

-- 
Peter Stephenson <pws@cambridgesiliconradio.com>
Cambridge Silicon Radio, Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK                          Tel: +44 (0)1223 392070


  reply	other threads:[~2000-05-22 16:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-22 15:01 Andrej Borsenkow
2000-05-22 15:33 ` Peter Stephenson
2000-05-22 16:03   ` Andrej Borsenkow
2000-05-22 16:17     ` Peter Stephenson [this message]
2000-05-22 16:35       ` Andrej Borsenkow
2000-05-22 17:04         ` Peter Stephenson
2000-05-23  0:19           ` Bart Schaefer
2000-05-23  0:43             ` Bart Schaefer

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=0FUY009QZYKZGE@la-la.cambridgesiliconradio.com \
    --to=pws@cambridgesiliconradio.com \
    --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).