Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Tue, 21 Mar 2000 16:37:43 -0500 To: Cygwin Subject: Re: pathname with spaces causes problems for tcsh Message-ID: <20000321163743.B21027@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cgf@cygnus.com, Cygwin References: <20000321205201.25071.qmail@web112.yahoomail.com> <200003212109.QAA25555@hrothgar.gw.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: <200003212109.QAA25555@hrothgar.gw.com>; from christos@zoulas.com on Tue, Mar 21, 2000 at 04:09:26PM -0500 On Tue, Mar 21, 2000 at 04:09:26PM -0500, Christos Zoulas wrote: >On Mar 21, 12:52pm, earnie_boyd@yahoo.com (Earnie Boyd) wrote: >-- Subject: Re: pathname with spaces causes problems for tcsh > >| Pathnames with spaces are a problem, period. By the time that pushd got the >| argument the backslashes had been removed and pushd passed to setenv more than >| one argument thus the complaint. >| >| You'll have to modify the source of tcsh to fix this problem. >| >| Earnie. >| >| P.S.: This problem would exist on UNIX if the directory contained spaces. > >No it would not. chdir("foo bar") works fine as well as >setenv/putenv("foo bar", "bar baz"). The problem is in the way >the interface call to the win32 setenv is implemented. I'm not sure what you mean by "interface call" but it's not likely that cygwin itself is doing something bad with environment variables with spaces in them. There is no parsing to be done (besides possibly looking for an '=') by the time the putenv or setenv is invoked by the DLL. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com