From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Faylor To: jeffdb@goodnet.com, cygwin@sourceware.cygnus.com Subject: Re: Here documents in ash shell scripts mess up stdin on 9x Date: Sat, 13 Feb 1999 21:40:00 -0000 Message-id: <19990214004131.A2408@cygnus.com> In-reply-to: < 36c7283a.158332818@mail.goodnet.com >; from Mikey on Sun, Feb 14, 1999 at 02:16:44AM +0000 References: <36c4737f.46513371@mail.goodnet.com> <36C4874D.71585466@paul.rutgers.edu> <36c4cded.69666249@mail.goodnet.com> <19990213164222.D590@cygnus.com> <36c7283a.158332818@mail.goodnet.com> <36c7283a.158332818@mail.goodnet.com> X-SW-Source: 1999-02/msg00443.html On Sun, Feb 14, 1999 at 02:16:44AM +0000, Mikey wrote: >The subject is here documents in ash, not ash bugs in general. > >The other bug that I noticed that caused me to go back to B19 ash is >that B20 ash fails to read/execute $SHINIT, which is how I get it to >read ~/.shrc on startup. > >Sorry Chris, I know you did most of the work on "upgrading" ash, but I >really can't see the point to adding console math functions in an sh >compatible shell. I don't recall them being there in svr4, but maybe >my memory is bad? It's possible, if you think that /bin/sh should do something with a SHINIT variable. That's not standard behavior. If I inadvertantly added "console math functions" then it was inattention on my part when I merged the Debian changes. I will take a look at stripping out any baggage that I added. I've seen people complaining about the supposed HERE document problems in ash on Windows 95. So far that is the only problem I've heard that sounds remotely like a real problem. Most of the other "problems" are complaints from people who think that ash should behave exactly the same way as bash except for being smaller and faster. cgf From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Faylor To: jeffdb@goodnet.com, cygwin@sourceware.cygnus.com Subject: Re: Here documents in ash shell scripts mess up stdin on 9x Date: Sun, 28 Feb 1999 23:02:00 -0000 Message-ID: <19990214004131.A2408@cygnus.com> References: <36c4737f.46513371@mail.goodnet.com> <36C4874D.71585466@paul.rutgers.edu> <36c4cded.69666249@mail.goodnet.com> <19990213164222.D590@cygnus.com> <36c7283a.158332818@mail.goodnet.com> X-SW-Source: 1999-02n/msg00435.html Message-ID: <19990228230200.grhD65lRfSeYMMiXZKGLJCv2vXzfC58l0gQ9FDqAuJo@z> On Sun, Feb 14, 1999 at 02:16:44AM +0000, Mikey wrote: >The subject is here documents in ash, not ash bugs in general. > >The other bug that I noticed that caused me to go back to B19 ash is >that B20 ash fails to read/execute $SHINIT, which is how I get it to >read ~/.shrc on startup. > >Sorry Chris, I know you did most of the work on "upgrading" ash, but I >really can't see the point to adding console math functions in an sh >compatible shell. I don't recall them being there in svr4, but maybe >my memory is bad? It's possible, if you think that /bin/sh should do something with a SHINIT variable. That's not standard behavior. If I inadvertantly added "console math functions" then it was inattention on my part when I merged the Debian changes. I will take a look at stripping out any baggage that I added. I've seen people complaining about the supposed HERE document problems in ash on Windows 95. So far that is the only problem I've heard that sounds remotely like a real problem. Most of the other "problems" are complaints from people who think that ash should behave exactly the same way as bash except for being smaller and faster. cgf