Unix deficiencies/problems

[Usenet file owner]

In article <8892 at csli.Stanford.EDU> gandalf at csli.stanford.edu (Juergen Wagner) writes:
>In article <1528 at cmx.npac.syr.edu> gefuchs at logiclab.cis.syr.edu (Gill E. Fuchs) writes:
>>one difficulty with unix (maybe local to the domains i've seen only)
>>is the immediate i/o feedback syndrom:
>>
>>what do i mean?
>>
>>well, suppose one types into the read-a-head buffer some 23 commands.
>>the commands echo immediately, not later in their appropriate location.
>
>Umm... How do you know the third command doesn't fail? What if it fails?
>What if you have a typo in the second command?

  I watch the output, and hit control-X to cancel the third command if
the second command fails.

>Don't do it! Typing ahead some 23 commands is not necessary. If you want to
>execute a sequence of 23 command, put them on a line, separated by ';', or
>even better, put them into a file (since you might want to reuse this sequence
>later).

  I know it isn't necessary.  I can type in a command, press return,
wait for it to finish, type another command, press return, wait for it
to finish, ....  But it's much faster to use typeahead.  Having it
echo in the middle of my output is quite annoying, though.  (Then
again, I worked with Apple ][, IBM-PC, and VMS systems--which have
typeahead working "right"--before I worked with UNIX; maybe one gets
used to this weirdness eventually.)
  Does anyone know the original reason for the immediate echoing?

+---------------------------+------------------------+-------------------+
| Anton Rang (grad student) | "VMS Forever!"         | VOTE on	         |
| Michigan State University | rang at cpswh.cps.msu.edu | rec.music.newage! |
+---------------------------+------------------------+-------------------+
| Send votes for/against rec.music.newage to "rang at cpswh.cps.msu.edu".   |
+---------------------------+------------------------+-------------------+