guido@mcvax.UUCP (Guido van Rossum) (06/05/84)
> In ANSI, it no longer understands CR, LF, ... Huh? The ANSI driver we've got (with DOS 2.00) works OK here: CR = same line, col. 1; LF = next line (may have to scroll), same column. Admittedly, in BASIC, both mean next line, col. 1; but this rather unfortunate anyway, and not the standard meaning of those characters. > There is a separate `cursor' location for characters written to the > ANSI screen port, so cursor motion under ANSI followed by plain > "PRINT"s (in basic) don't do what you want. I guess this problem is caused by BASIC (which does its own screen buffering etc.) rather than by the ANSI driver. Apparently BASIC does not interface with DOS the way it "should" (i.e. use DOS function calls for I/O). All in all, I am quite happy with the ANSI driver: the only bug I know of (published earlier here) is that ctrl-P is sometimes taken to be the same as ctrl-PrtSc (silly!). But it took me some time before I realized that to use it from BASIC you have to OPEN "CON" FOR OUTPUT AS #... . And I would like some extensions such as insert/delete line/character. Yet, with a simple BASIC program as terminal interface and a tailored termcap entry, I can use my, sorry, our PC as terminal and even run "vi". (Emacs is somewhat problematic because it doesn't like ctrl-S/ctrl-Q flow control, and because of the ctrl-P problem.) -- Guido van Rossum, "Stamp Out BASIC" Committee, CWI, Amsterdam guido @ mcvax ^^^^^ (...How come I am discussing BASIC programs here?)