X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3111A3985447
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1610129633;
	bh=7e07Csd+tXaAmwedv/3WyNfD70xdxhN/fRjg5uzkmWI=;
	h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=yIL29/IRKzNi1xw4F0nl6CPheZe6Ko1LwwjyDTxQMtwr5gF9IsccaWYtcjw66vL7B
	 zuRiLVEPBQbLDctnvuyOf4dTlrMlTlVGrBYrvryKfbeFViBc0t7lCNZsQDm4LrEPbR
	 CYePez+tb0uh0PIFTkP0Nw0kjHuy7RUQ3UHGFzIY=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 27AAE38438A3
X-Authority-Analysis: v=2.4 cv=Q4RsX66a c=1 sm=1 tr=0 ts=5ff8a0dd
 a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17
 a=IkcTkHD0fZMA:10 a=uYT-Tk0qkVT609LjNaIA:9 a=QEXdDO2ut3YA:10
Subject: Re: Limitation of setenv for tcsh: Too many arguments
To: cygwin AT cygwin DOT com
References: <0d66260ff1314bf693caa6cbb6647547 AT BELBRU-EXMP101 DOT eeas DOT europa DOT eu>
 <4a7542e2-9f38-9e72-3229-ca39feab66d1 AT cs DOT umass DOT edu>
Organization: Inglis
Message-ID: <36f296b6-55ff-cca5-10dc-4e1df7a68147@Shaw.ca>
Date: Fri, 8 Jan 2021 11:13:48 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <4a7542e2-9f38-9e72-3229-ca39feab66d1@cs.umass.edu>
Content-Language: en-CA
X-CMAE-Envelope: MS4xfDFePMsot1lIKVx/pmVwhp+3vbNFPV2d0FOg9ne3PZ5xAe8lIii4s8Em1EwGYom4lo95AToZ2LhtUs19qmoBMb+Oz14h6PAeqw7vi2PANAlY07zNDrx7
 RN89B6uRXsRHTDJxRxdEAq02vFNUErEhj7K87QM2EYqMkAgOf+cvU5ACa2D0bVNZ1ymWsp9o5KApFQ==
X-Spam-Status: No, score=-3.6 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_LOW,
 RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Brian Inglis via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Brian DOT Inglis AT Shaw DOT ca
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: cygwin-bounces AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 108IEKZu016290

On 2021-01-08 06:21, Eliot Moss wrote:
> On 1/8/2021 5:13 AM, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
>  > Dear all,
>  >
>  > There is a limitation for tcsh (setenv: Too many arguments) to set the PATH 
> environmental variable as you can see in the attached file with the steps to 
> reproduce it. It probably looks like tcsh limitation and not Cygwin. The "set 
> path=( ${HOME}/bin $path)" is not complaining and sets the path, but it also 
> interprets the space in the paths as a separator. The only Cygwin related issue 
> is probably the /usr/bin that it is added twice. Any workarounds?
> 
> I saw another response, but will add that I typically do something more like:
> 
> set PATH="${HOME}/bin:${PATH}"
> 
> THat takes care of quoting.  However, you want to avoid duplicate entries.
> Something like this helps with that:
> 
> [ -z "${PATH##*${HOME}/bin:*}" ] || {
>    PATH="${HOME}/bin:${PATH}"
> }
> 
> I suppose it is slightly dangerous in that it would also match
> /foo/${HOME}/bin, but ${HOME} is absolute and such a match seems unlikely.
> Still, you could do:
> 
> [ -z "${PATH##${HOME}/bin:*}" ]
> 
> to check if it is first on the path, and
> 
> [ -z "${PATH##*:${HOME}/bin:*}" ]
> 
> to see if it is in the middle, and
> 
> [ -z "${PATH##*:${HOME}/bin}" ]
> 
> to see if it as at the end.  This leads to:
> 
> [ -z "${PATH##${HOME}/bin:*}" ] || [ -z "${PATH##*:${HOME}/bin:*}" ] || [ -z 
> "${PATH##*:${HOME}/bin}" ] || {
>    PATH="${HOME}/bin:$PATH}"
> }
> 
> Because of the three first/middle/end possibilities, this is what comes to
> mind.  _Maybe_ you could get a more elegant solution using bash arrays, but
> this is not that long as a piece of bash code.

Please consider the subject line - he is using tcsh in which path is an array - 
Achim followed up with hints on handling the issues under that shell! ;^>

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple