Some comment about Cygwin1.1.4
Chris Faylor
cgf@cygnus.com
Tue Aug 8 07:50:00 GMT 2000
On Tue, Aug 08, 2000 at 10:33:00AM -0400, Noel L Yap wrote:
>What's the behaviour of this when running csh or tcsh?
Who knows? Who cares? This is intended to distinguish between ash and bash.
cgf
>cgf@cygnus.com on 2000.08.08 10:19:52
>
>Please respond to cygwin@sources.redhat.com
>
>To: cygwin@sources.redhat.com
>cc: dj@cygnus.com (bcc: Noel L Yap)
>Subject: Re: Some comment about Cygwin1.1.4
>
>
>
>
>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?
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
More information about the Cygwin
mailing list