Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: _ssh (scp)
- X-seq: zsh-workers 16554
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: Clint Adams <clint@xxxxxxx>, zsh-workers@xxxxxxxxxx
- Subject: Re: PATCH: _ssh (scp)
- Date: Mon, 4 Feb 2002 18:25:01 +0000
- Cc: david@xxxxxxxxxx
- In-reply-to: <20020204175927.GA12977@xxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20020204175927.GA12977@xxxxxxxx>
On Feb 4, 12:59pm, Clint Adams wrote:
} Subject: PATCH: _ssh (scp)
}
} So this is based on a patch from David Engel for something resembling
} the current 4.0.x CVS. Is it necessary to provide the echo behavior
} as well, or can we safely assume that everything can do ls -d1F these
} days?
Assorted remarks:
This still needs the 2>/dev/null fix I described in 16533.
If you *are* going to parse "ls -F" output, you should remove the comment
that indicates otherwise.
Another possible approach would be to use ls (without -d) on the directory
parent of the remote path, and let the completion system filter out the
non-matching names, rather than the rather crude hack I did of appending
a `*' to the path. This would support complete-in-word a bit better, but
means more network traffic.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
Messages sorted by:
Reverse Date,
Date,
Thread,
Author