From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Limitation of setenv for tcsh: Too many arguments
Date: Fri, 08 Jan 2021 11:38:31 +0100 [thread overview]
Message-ID: <871revlnmg.fsf@Otto.invalid> (raw)
In-Reply-To: <0d66260ff1314bf693caa6cbb6647547@BELBRU-EXMP101.eeas.europa.eu> (KAVALAGIOS Panagiotis's message of "Fri, 8 Jan 2021 10:13:25 +0000")
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.
As an aside, it is highly unlikely that you'd actually want to set up
your PATH like that.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2021-01-08 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 10:13 KAVALAGIOS Panagiotis (EEAS-EXT)
2021-01-08 10:38 ` ASSI [this message]
2021-01-08 10:55 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2021-01-08 16:19 ` Achim Gratz
2021-01-11 8:11 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2021-01-11 15:34 ` Eliot Moss
2021-01-08 13:21 ` Eliot Moss
2021-01-08 18:13 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871revlnmg.fsf@Otto.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).