Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!xanth!mcnc!thorin!alanine!leech
From: leech@alanine.cs.unc.edu (Jonathan Leech)
Newsgroups: comp.lang.c
Subject: Re: printf, data presentation
Message-ID: <6177@thorin.cs.unc.edu>
Date: 15 Jan 89 05:39:09 GMT
References: <19@xenlink.UUCP> <225800106@uxe.cso.uiuc.edu> <310@twwells.uucp> <411@ispi.UUCP>
Sender: news@thorin.cs.unc.edu
Reply-To: leech@alanine.UUCP (Jonathan Leech)
Followup-To: comp.terminals
Organization: University Of North Carolina, Chapel Hill
Lines: 25
Summary:
Expires:
Sender:
Distribution:
Keywords:

In article <411@ispi.UUCP> jbayer@ispi.UUCP (Jonathan Bayer) writes:
>In article <310@twwells.uucp> bill@twwells.UUCP (T. William Wells) writes:
>>And many terminals are incapable of transmitting characters as they
>>are typed.
>I don't know about what terminals you are using, but most (if not all)
>serial terminals ARE capable of transmitting characters as they are
>typed.

    IBM 3270-style block mode terminals have this "feature".  I've
used Unix (Amdahl UTS/580) on such terminals, and it's painful. The
usual editors don't work, ksh loses, etc (but hey! you get hardware
pagination). There are a *lot* of block mode terminals in the world.
Fortunately, most of them aren't connected to Unix systems.

    Some of the same problems can arise when working over packet
networks (X.25) that don't support break after every character.
You wouldn't want them to in any case, since charging is frequently on
a per packet basis :-)

    Followups to comp.terminals.
--
    Jon Leech (leech@cs.unc.edu)    __@/
    ``My goal is simple. It is complete understanding of the universe,
      why it is as it is and why it exists at all.''
	- Stephen Hawking