Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com X-Authentication-Warning: tweedle.cabbey.net: cabbey owned process doing -bs Date: Wed, 7 Feb 2001 22:42:58 -0600 (CST) From: Christopher Abbey X-Sender: cabbey AT tweedle DOT cabbey DOT net To: cygwin AT cygwin DOT com Subject: RE: bash: setenv: command not found In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Today, Jeff Lu wrote: > $ info --file /usr/info/bash > info: /usr/info/bash: No such file or directory iirc Corinna just recently added / was asked to add that file, so it's not too surprising it failed for you. > BTW, what is > FOO=bar' and `unset FOO'. the answers to your question. setenv/unsetenv are commands that are built into the csh family of shells. Under bash the equivalent built ins are export and unset. For example: CSH: setenv name value BASH: export name=value CSH: unsetenv name BASH: unset name yes, this is a stupid naming convention, and it's one of the things I hate the most about shells... every one has a different version, and different syntax. There needs to be ONE standard, and I'm sorry to say BASH's answer isn't an answer; here csh got it right. -- now the forces of openness have a powerful and unexpected new ally - http://ibm.com/linux -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple