Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <5.2.0.9.2.20030402104347.02cb6cc0@pop3.cris.com> X-Sender: rrschulz AT pop3 DOT cris DOT com Date: Wed, 02 Apr 2003 10:47:51 -0800 To: cygwin AT cygwin DOT com From: Randall R Schulz Subject: RE: complete.tcsh doesn't handle spaces in $HOME In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Hannu, Here's the full set of recommendations: Yours: Stick to [A-Za-z0-9-_.] characters in filenames, settings and such. Plus: Write all your scripts to accommodate the presence of spaces and shell metacharacters in file names. >This is a true pain in the ass... I wish everybody could stick to >iso-8859-1 or its siblings. This is unrealistic, chauvinistic and atavistic. Randall Schulz At 10:35 2003-04-02, you wrote: > > From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf > > Of Aaron Humphrey > > > An easy workaround for this problem is just to wrap all of the > > $HOME/filename conditions in double quotes, which would probably > > be a good idea in a future release of tcsh. Once I did this in > > complete.tcsh, tcsh started up just fine. > >My experience is: > You can expect to have the exact same problem with quite a few >scripts and other software. > >My advice: > Stick to [A-Za-z0-9-_.] characters in filenames, settings and such. > >Sad to say, this does apply for almost any other "OS" too `:-P > >/Hannu E K Nevalainen, Mariefred, Sweden -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/