Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <398F34C5.D28A1006@veritas.com> Date: Mon, 07 Aug 2000 15:14:29 -0700 From: Bob McGowan Organization: VERITAS Software X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: DJ Delorie CC: cygwin@sources.redhat.com Subject: Re: Some comment about Cygwin1.1.4 References: <398EF5AD.97DC2CEC@onera.fr> <200008071749.NAA01544@envy.delorie.com> <398EFA1C.6EC280E7@onera.fr> <200008071834.OAA01863@envy.delorie.com> <398F0A7F.CD49D864@vinschen.de> <200008071916.PAA02265@envy.delorie.com> <398F0F75.82839993@veritas.com> <200008071937.PAA02475@envy.delorie.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit DJ Delorie wrote: > > > By default, it should not be exported, but a user could export it > > themselves. > > Stupid Linux. sh -> bash. OK, if I run *ash* you're right. Yes, this has caught me a number of times, too. > I'm thinking, though, that this won't help anything. If the user just > types "sh" at a bash prompt, there aren't any files sourced by sh > where we'd get a chance to fix the prompts. True, if that is what was wanted. I was thinking only in terms of a "login" shell. And, on all UNIX/Linux systems I've used, if the user starts a subshell that uses common env variables but does not understand advanced features available in the parent, the result is displayed wihtout interpretation, so this is working "as expected". -- Bob McGowan Staff Software Quality Engineer VERITAS Software rmcgowan@veritas.com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com