Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!world!geoff
From: geoff@world.std.com (Geoff Collyer)
Newsgroups: comp.unix.wizards
Subject: Re: POSIX bashing (actually cooked vs raw or cbreak mode)
Message-ID: <1991Apr10.192226.24909@world.std.com>
Date: 10 Apr 91 19:22:26 GMT
References: <3419@unisoft.UUCP> <5980071@hpfcdc.HP.COM> <3446@unisoft.UUCP> <15621@smoke.brl.mil> <70319@brunix.UUCP> <3478@unisoft.UUCP> <71479@brunix.UUCP>
Organization: The World @ Software Tool & Die
Lines: 16

Curtis Yarvin:
>Isn't it better to get the choice out of the kernel, and let each
>application decide what it wants?

No, it isn't.  The last thing I want is each application having a
different idea of what I have to type to erase input (for example).
`Gee, now I'm in emacs, so I have to type control-A control-K to erase my
line.' Ugh.  One of the great wins of Unix is that it lets the *user*
make such choices, not J. Random Losing Application (unless it switches
to cbreak mode, which is becoming distressingly common).  This is one
reason that cooked mode is a win (fewer context switches being the other
obvious one) and that shell globbing is a win: they are done centrally,
by one piece of code, so they work uniformly and all applications and
users benefit.  (Yeah, we know about "restore *".)
-- 
Geoff Collyer		world.std.com!geoff, uunet.uu.net!geoff