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 From: "Hannu E K Nevalainen (garbage mail)" To: "Aaron Humphrey" , Subject: RE: complete.tcsh doesn't handle spaces in $HOME Date: Wed, 2 Apr 2003 20:35:26 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 > 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 -- Exception: Umlauted, careted and apostrophed characters does work, given that the correct settings has been provided. Note though that setting has to be provided for many programs separately. e.g. Bash, ls, emacs, ... This is a true pain in the ass... I wish everybody could stick to iso-8859-1 or its siblings. --END OF MESSAGE-- -- 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/