X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:reply-to; q=dns; s=default; b=x4u51LFTl9RyfQsbIawpZXBAsWqzIAnpf
	BjRvdvBlmXqgKFfYLotIZHxcenPgCr7akHYQ3KRtc+Z7VP0wbdnhwoXfTg8kE2uq
	FztNXWU2iEZVMIOKX3wYbOt9tGACFun14IlSgUJz6dxTlgYY+D0umkXKNXM0Jy+H
	p9GqmTaxds=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:reply-to; s=default; bh=2kmJhr1m72qg9kgtkt+9BjA5a7w=; b=GXmy8EG
	GoHAWemvlSmsU+okA6lnpA2Km+tZ+YQMwdNiwR6WdUTOPqCshFB3i5BP0ScQSbQc
	cNXs+2D5cAp0yfJcIxsC6XqqcqFEOS6OtKInyE0eW0xzZ5jSq1koo25No3KlE7HQ
	BUzDESQmJDandml7mgjbtpgMZ7zc1nIjLZPM=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=HZA-ZIC2, HZAZIC2, hza-zic2, hzazic2
X-HELO: blaine.gmane.org
To: cygwin AT cygwin DOT com
From: Will Parsons <wbp AT nodomain DOT invalid>
Subject: [SOLVED] Re: tcsh path conversion messed up?
Date: Tue, 7 Nov 2017 22:07:53 +0000 (UTC)
Lines: 48
Message-ID: <ottaro$v2$1@blaine.gmane.org>
References: <oto9is$k56$1 AT blaine DOT gmane DOT org> <otqlbj$91n$1 AT blaine DOT gmane DOT org> <otqlvg$bcf$1 AT blaine DOT gmane DOT org> <d9ac360f-c14d-5bd9-b2f5-54dceefd4449 AT SystematicSw DOT ab DOT ca> <8ef62c62e13846dd80c1ba65397b8a67 AT DE013666 DOT schaeffler DOT com>
Reply-To: wbparsons AT cshore DOT com
User-Agent: slrn/1.0.3 (CYGWIN_NT-6.1)
X-IsSubscribed: yes

Lemke, Michael  ST/HZA-ZIC2 wrote:
> On Tuesday, November 07, 2017 7:12 AM Brian Inglis wrote:
>>On 2017-11-06 14:59, Will Parsons wrote:
>>> Will Parsons wrote:
>>>> I asked about what I thought was a shell scripting problem:
>>>>    PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/c/Windows/system32:/c/Windows:/c/Windows/system32/wbem:/c/ProgramData/Oracle/Java/javapath:/c/Program:Files/Common:Files/Microsoft:Shared/Windows:Live:/c/Program:Files:(x86)/Common:Files/Microsoft:Shared/Windows:Live:/c/Program:Files/Dell/DW:WLAN:Card:/c/Program:Files:(x86)/Intel/iCLS:Client:/c/Program:Files/Intel/iCLS:Client:/c/Windows/System32/WindowsPowerShell/v1.0:/c/Program:Files/WIDCOMM/Bluetooth:Software:/c/Program:Files/WIDCOMM/Bluetooth:Software/syswow64:/c/Program:Files:(x86)/Windows:Live/Shared:/c/Program:Files:(x86)/Bazaar:/c/Program:Files:(x86)/QuickTime/QTSystem:/c/cygwin/home/william/bin:/c/ezwinports/bin:/c/Program:Files:(x86)/PuTTY:/usr/lib/lapack
>>>>
>>>> This doesn't look right, and would explain the strange shell output I
>>>> reported.  (The value of PATH under bash looks normal.)  Did the installation
>>>> of tcsh somehow get corrupted?  I don't remember a particularly recent update
>>>> to tcsh.
>
> How are you setting path? Do you have anything in your .cshrc/.login file? Most
> likely, you are doing it wrong. 
>
>>> Another bit of info - I just noticed that the value of the (t)csh shell
>>> variable 'path' is:
>>
>>In csh, "PATH" is a standard Unix environment variable whose value is a colon
>>separated directory list, and "path" is a shell wordlist kept synchonized with
>>"PATH".
>>To list the wordlist entries with embedded spaces in csh, quote the variable
>>name with the :q modifier in a foreach loop wordlist, and you get the desired
>>result as easily as in your sh script [trimmed and ...s redacted]:
>>
>>.......% foreach p ( $path:q )
>>foreach?	echo $p
>>foreach? end
>
> And that is also key for setting path:
>
> set path = ( ... $path:q )
>
> I had this bug ($path instead of $path:q) for 20 years in my init files.

Bingo!  I had this line in my ~/.cshrc:

  set path = ( /usr/local/bin /usr/bin /bin /usr/sbin $path )

Changing $path to $path.q solved the problem.

(I am still somewhat puzzled, though - the original PATH that I quoted in my
original query did have spaces, so what changed?)

At any rate, the problem seems to be solved, so thank you very much.

-- 
Will


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple