[GreenKeys] [Bulk] Re: C-64 to drive Mdl. 15 TTY (and probably others..)

[Dave Horsfall]

On Fri, 4 Sep 2015, drlegendre . wrote:

> I think I've understood the reason to send the LTRS shift (not sure why 
> +two+ times, but whatever) as if the last shift is FIGS it leaves the 
> remote machine in FIGS. This would mean the remote typist might 
> accidentally send FIGS chars when they believe the machine is in LTRS 
> shift. Thus the courtesy, correct? 

Two, in case one is lost through static/fading etc.  I think this was 
before FEC/ARQ etc.

> Also, sequential CR chars have no effect, other than to busy the line, 
> once the first CR makes it to the other machine - right? Multiple LFs 
> would be another matter, then..

It was to allow time to allow the Carriage to Return; these things are 
about as old and slow and crusty as their owners :-)

Dunno about multiple LFs; worst you'll do is waste a line of paper, but
the best you'll
                do
		   is
		      avoid
			    this.

(Please view in a fixed-width non-adjusting font, as I refuse to use HTML.)

> As far as the char-per-line count, it never struck me that the receiving 
> machine wouldn't be able to sense the EOL limit and make a CR/LF (wrap 
> the text) when needed, like any 'smart' terminal should. So on the 
> driver side, I need to keep track of the number of (printable..) chars 
> since the last CR/LF - and send a CR/LF pair when the length exceeds the 
> limit - do I have that right? 

Well, the receiver has been told what to do, so if you send a really long line, well...

(Best viewed with a "real" 80-char box, BTW, not a dumb browser.)

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
 Concerned about shark attacks?  Then don't go swimming in their food bowl...