zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Clint Adams <clint@zsh.org>, zsh-workers@sunsite.dk
Cc: david@debian.org
Subject: Re: PATCH: _ssh (scp)
Date: Mon, 4 Feb 2002 18:25:01 +0000	[thread overview]
Message-ID: <1020204182501.ZM21407@candle.brasslantern.com> (raw)
In-Reply-To: <20020204175927.GA12977@dman.com>

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   


  reply	other threads:[~2002-02-04 18:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-04 17:59 Clint Adams
2002-02-04 18:25 ` Bart Schaefer [this message]
2002-02-04 18:43   ` Clint Adams
2002-02-05 10:24 ` Oliver Kiddle
2002-02-05 17:47   ` Clint Adams
2002-02-05 18:08     ` Clint Adams
2002-02-05 18:38       ` Bart Schaefer
2002-02-06 16:43         ` Clint Adams
2002-02-06 16:59           ` Borsenkow Andrej
2002-02-06 18:12             ` The :h modifier Brass Lantern Enterprises

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=1020204182501.ZM21407@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=clint@zsh.org \
    --cc=david@debian.org \
    --cc=zsh-workers@sunsite.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).