Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Tue, 8 Aug 2000 10:19:52 -0400
To: cygwin AT sources DOT redhat DOT com
Cc: DJ Delorie <dj AT cygnus DOT com>
Subject: Re: Some comment about Cygwin1.1.4
Message-ID: <20000808101952.E20147@cygnus.com>
Reply-To: cygwin AT sources DOT redhat DOT com
Mail-Followup-To: cygwin AT sources DOT redhat DOT com, DJ Delorie <dj AT cygnus DOT com>
References: <398EF5AD DOT 97DC2CEC AT onera DOT fr> <200008071749 DOT NAA01544 AT envy DOT delorie DOT com> <398EFA1C DOT 6EC280E7 AT onera DOT fr> <200008071834 DOT OAA01863 AT envy DOT delorie DOT com> <398F0A7F DOT CD49D864 AT vinschen DOT de> <200008071916 DOT PAA02265 AT envy DOT delorie DOT com> <398F0F75 DOT 82839993 AT veritas DOT com> <398FDC2B DOT 55986AC7 AT telia DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.6i
In-Reply-To: <398FDC2B.55986AC7@telia.com>; from c.christian.joensson@telia.com on Tue, Aug 08, 2000 at 12:08:43PM +0200

I usually do something like:

(alias a=b) >/dev/null 2>&1 && echo "we're running bash"

to detect which shell is in use.

cgf

On Tue, Aug 08, 2000 at 12:08:43PM +0200, Christian J?nsson wrote:
>What about trying to execute "display-shell-version (C-x C-v)". If
>we're in a bash shell, we'd get the verision info (works on both
>bash1 and bash2) and I suppose that if we're on (a)sh we'd get nothing.
>
>Cheers,
>
>/ChJ
>
>
>Bob McGowan wrote:
>> 
>> DJ Delorie wrote:
>> >
>> > > echo $BASH_VERSION ?
>> >
>> > No, because if you run sh from bash, it may inherit that environment
>> > variable.
>> 
>> By default, it should not be exported, but a user could export it
>> themselves.
>> 
>> How about a double check of RANDOM?  If it gets exported, the inherited
>> value in (a)sh appears to be constant, while in bash it changes with
>> each access.  The only problem I can see with this is that a user could
>> unset RANDOM, then make a new variable with that name, but which will
>> not have the special feature.  I would think that this is rare enough to
>> maybe be ignored?
>> 
>> --
>> Bob McGowan
>> Staff Software Quality Engineer
>> VERITAS Software
>> rmcgowan AT veritas DOT com
>> 
>> --
>> Want to unsubscribe from this list?
>> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
>
>--
>Want to unsubscribe from this list?
>Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

-- 
cgf AT cygnus DOT com                        Cygnus Solutions, a Red Hat company
http://sourceware.cygnus.com/         http://www.redhat.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com