> -----Original Message-----
> From: Cygwin <cygwin-boun...@cygwin.com> On Behalf Of ASSI
> Sent: 08 January 2021 11:39
>
> KAVALAGIOS Panagiotis (EEAS-EXT) writes:
> > 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?
>
> Both problems are a failure on your part to quote the arguments correctly.
> Consult the documentation for the respective shell to find enlightenment.
Indeed, I forgot the double quotes. That works:
setenv PATH "${HOME}/bin:${PATH}"
I confused the message like a length limitation and not for the number of input
arguments.
Why do you say both? I don't add /usr/bin anywhere.
> As an aside, it is highly unlikely that you'd actually want to set up your
> PATH
> like that.
Care to explain? How else can I add in the path custom personal commands?
Panos
Application Architect
CONSULIAT (under contract with the EEAS)
BA.BS.3.IS
Office: EEAS B100 Floor 5 Area 048
Rue Belliard 100, 1000 Brussels
Phone: +32 2 584 6017
--
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
