Subject: bin/6951: Filename completion in ftp fails for filenames including blanks
To: None <gnats-bugs@gnats.netbsd.org>
From: None <simons@cys.de>
List: netbsd-bugs
Date: 02/06/1999 18:22:04
>Number: 6951
>Category: bin
>Synopsis: Filename completion in ftp fails for filenames including blanks
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: bin-bug-people (Utility Bug People)
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sat Feb 6 09:35:01 1999
>Last-Modified:
>Originator: Peter Simons
>Organization:
>Release: NetBSD 1.3.2
>Environment:
System: NetBSD peti.cys.de 1.3.2 NetBSD 1.3.2 (PETI) #0: Thu Dec 10 16:06:47 CET 1998 simons@peti.cys.de:/usr/src/sys/arch/i386/compile/PETI i386
>Description:
The ftp client distributed with NetBSD thankfully supports file name
completion on files lying on the remote server. Unfortunately this
mechanism produces incorrect results for filennames which include
blanks -- and probably other special characters.
Let's assume on the remote server exists a file of the name "complete
me" and you'd want to GET it. So you'd type "GET com<tab>" and get the
command line "get complete me" as a result. But the GET won't work,
because the name has to be written in quotes in order to work.
Bash remedies this problem by escaping the blanks in question with a
backslash. I propose that this is added to the ftp client code, too.
>How-To-Repeat:
>Fix:
>Audit-Trail:
>Unformatted: