jdi@psuvax.UUCP (01/24/84)
Two interesting things I just found out about with virtterm (the terminal driver for vnews, which is really quite nice) 1: It appears to have some problems with some termcap entries that have a 'ho' (home) field. On a z29, especially, it likes to dump core by completely messing up the stack. This may, however, be a termcap problem. A quick fix is to take out the 'ho' entry, which prevents virtterm from trying that route of optimization, but I hate kludging. 2: Unless I am sadly mistaken virtterm simply will NOT work with terminals that have a 'cs' (set scrolling region) entry. (Also, it's sort of interesting that the vt100 termcap entry DOESN'T have this) What happens is apparently that virtterm calls tgoto at some time with what it thinks is the 'cs' string. Well, termcap thinks differently and prints 'OOPS'. (at first I thought it was the z29, that was REAL strange) Anyway, does anyone have any fixes/suggestions for these problems? -- Spoken: John Irwin AT&T: 814-237-5068 Net: jdi@psuvax1.BITNET jdi@penn-state.CSNET UUCP: {akgua, allegra, cornell, ihnp4, burdvax}!psuvax!jdi
ra@rlgvax.UUCP (Rick Adams) (01/25/84)
Well, I am running vnews on a vt100 with the "cs" entry with no problems. I did have some initial problems, but they turned out the be an incorrect entry in the vt100 termcap entry.