This is the mail archive of the
mailing list for the Cygwin project.
Re: Why 'script' utility require SHELL (and work fine under Linux)?
- From: Cyrille Lefevre <cyrille dot lefevre-lists at laposte dot net>
- To: cygwin at cygwin dot com
- Date: Fri, 04 Nov 2011 06:05:39 +0100
- Subject: Re: Why 'script' utility require SHELL (and work fine under Linux)?
- References: <email@example.com>
Le 14/10/2011 11:43, Oleksandr Gavenko a Ãcrit :
Look to my session:
well, you session isn't very clear, however...
As you can see first time script does not use SHELL, second time use it
and third tie use it.
So SHELL env var does not exported by bash...
well, shells doesn't export anything except variables already
exported at shell invocation or using the export builtin.
so, under unix like, $SHELL is positionned by login or whatever
process (sshd, telnetd, X gui, etc.) which launch the interactive
under cygwqin, $SHELL is well positionned when connected through the
network (sshd) but not when launched by cygwin.bat.
Is this right add
.bash_profile is more appropriate.
the base-file maintainer has been BCC'ed to add the export SHELL to the
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple