Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <392F0660.CFB8653@veritas.com> Date: Fri, 26 May 2000 16:18:56 -0700 From: Bob McGowan Organization: VERITAS Software X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: cygwin AT sourceware DOT cygnus DOT com Subject: Re: File name syntax (WAS: RE: FW: Can not config sshd) References: <20000526215054 DOT 0A742F805 AT mx1 DOT hotpop DOT com> <392EFA58 DOT 456793A7 AT veritas DOT com> <20000526190005 DOT A24112 AT cygnus DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Chris Faylor wrote: > > On Fri, May 26, 2000 at 03:27:36PM -0700, Bob McGowan wrote: > >If the decision stands to change bash, doesn't that imply a need to fix > >the other shells too? > > Have you seen a lot of traffic about other shells having this problem? > I don't recall any. No. But then, I also haven't seen a lot of traffic about people using lots of //server stuff in scripts, either ;-) I was simply trying to point out a potential problem area, since any application (shell or otherwise) working in a UNIX environment does not need to worry itself about multiple slash characters anywhere in a path name. So, by implication, any application that uses paths, could manifest this problem. And since the application can be started from either a command prompt or a shell, the further implication is that any application handling paths would now need modification to be aware of this special handling requirement. -- Bob McGowan Staff Software Quality Engineer VERITAS Software rmcgowan AT veritas DOT com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com