On Sun, Apr 22, 2001 at 10:03:28PM +1000, Robert Collins wrote: > > ----- Original Message ----- > From: "Corinna Vinschen" <[EMAIL PROTECTED]> > > > > That's really tricky: > > > > sh < foo O_TEXT? > > cat foo | sh O_BINARY? > > That looks correct to me. I had some trouble with awk a while back that > I haven't gotten around to fixing... and its the same difference. I > don't know whether it's up to the shell to set the input and output > types and let the app override, or whether it's just the apps problem... Only the app knows how it wants it's input so it has to care. A shell wants text, so it sets stdin to O_TEXT. Corinna
- ash stdin mode is set to O_TEXT egor duda
- Re: ash stdin mode is set to O_TEXT Christopher Faylor
- Re: ash stdin mode is set to O_TEXT egor duda
- Re: ash stdin mode is set to O_TEXT Earnie Boyd
- Re: ash stdin mode is set to O_TEXT Corinna Vinschen
- Re: ash stdin mode is set to O_TEXT egor duda
- Re: ash stdin mode is set to O_TEXT Robert Collins
- Re: ash stdin mode is set to O_TEXT Corinna Vinschen
- Re: ash stdin mode is set to O_TEXT Corinna Vinschen
- Re: ash stdin mode is set to O_TEXT Christopher Faylor
- Re: ash stdin mode is set to O_TEXT Corinna Vinschen
- Re: ash stdin mode is set to O_TEXT Christopher Faylor
- Re: ash stdin mode is set to O_TEXT egor duda
- Re: ash stdin mode is set to O_TEXT Corinna Vinschen
