apratt@iuvax.UUCP (04/21/84)
I have also noticed an interesting glitch in some tty driver or other: when you dial up at 300 baud, *something* somewhere is inserting a delay after each nl. At 1200 Baud, it goes away. The lights on my friend's Hayes modem go out, meaning that it is not receiving anything (not even nulls (I think)). Again, no amount of stty seems to affect this. ---- "Fritz! They've killed Fritz!" -- Allan Pratt ...ihnp4!inuxc!iuvax!apratt (please do not respond to iuvax!notes)
dmmartindale@watcgl.UUCP (Dave Martindale) (04/22/84)
v7 and later tty drivers derived from it (32V, 4.XBSD, etc) have several bits in the stty "mode" word which control the presence and length of various delays. In particular, you will probably find that one or more of the bits making up CRDELAY or NLDELAY is set (the manifests are in /usr/include/sgtty.h or somewhere similar). Stty should let you turn the delays off. The default delays you get, which may be different at different speeds, are set by /etc/getty. They may be compiled into tables inside getty or read from a file, depending on what version of UNIX you are dealing with. The most conservative assumption a system maintainer can make is that some terminals which dial up his machine may need delays, and so have them on by default.
jeff@alberta.UUCP (Curt Sampson) (04/26/84)
[The bug is there so I don't have to read all the dumb first lines.] I am running a terminal program on my computer, but it seems to drop the first character on every line, which is very annoying. I have tried using stty(1) with the nl# and cr# options, and also using the nl/cr delays in my termcap file, but nothing seems to work. Does anyone know if there is any way to convince UNIX to put a null out after every cr/nl pair? Thanks in advance. Curt Jeff Sampson alberta!jeff -- -- "Watch out, Mr. T. From Tuktoyatuk, it's the ** eh? Team **."