X-Spam-Check-By: sourceware.org Date: Mon, 18 Jun 2007 10:44:06 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: bug in tcsh 6.15.00-4 Message-ID: <20070618084406.GJ4179@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4674ED73 DOT 60708 AT zone42 DOT org> <20070618081123 DOT GI4179 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Jun 18 10:34, Steffen Sledz wrote: > On Mon, 18 Jun 2007, Corinna Vinschen wrote: > > It would be better in the long run *not* to use spaces in path names, > > though. It's not very tricky to set up and it helps to avoid annoying > > problems with shell scripts, etc. > > Sorry, i do not believe that this is acceptable. Nowadays it's quit common > to use spaces in path names (e.g. $HOME often points to "C:\Documents and > Settings\User" in XP). And shell script can (and should) be aware of this > if they are written carefully. Bad example. The path name "C:\Documents and Settings" is just a mess. Fortunately Microsoft replaced it in Vista by "C:\Users". Well, it's your choice. Spaces in path names were quite unnecessary to begin with. It's an erroneous trend which doesn't get better by being "common". It's still not common on non-Windows systems. And it's quite easy to get rid of them: $ mount -f -s -b C:/Documents and Settings" /home And with Vista this weird trend will hopefully rectified, at least partly. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/