dvadura@watdragon.waterloo.edu (Dennis Vadura) (02/16/89)
System: DN 3500
OS: SR 10.1
Ok, we have a whole bunch of machines on the internet around here.
I want to create a bunch of DM windows, and rlogin into the various machines.
(similar to what I do when I'm on a box with a whole bunch of X-windows)
I can do this trivially, but...
The only way I seem able to really do it well is using vt100, and then rlogin
(or vt100 rlogin host... etc), however, whenever I then perform an rlogin
from there to some other machine my whole window locks up. I can reproduce
this every single time (nuking it seems to be the only fix). I can also
freeze the window by typing at it the vt100 initialization/resize sequence
from the local termcap database, this is guaranteed to freeze all input into
the window, hence I figure it's the vt100 emulator that is going for a dive.
What I would really like though is to not use vt100 at all, and to just use
the DM window with an rlogin. This also works fine as long as I
pretend to be a dumb terminal. Alas this is no good for things like vi, rn,
and the list goes on.
Anyway, after staring into the 3 feet of documentation we have on Apollos here
I see no mention of a termcap like capabilities description for DM windows.
Does such a beast exist, if so does anyone have one. Better yet is there
a character sequence that a program can blast into a DM window that does
cursor positioning and the like, if so where in the documentation is a
description of the capabilities.
Am I doomed to using vt100 for ever? Actually I can probably wait for X, but
it just seems silly for there to be no way to do what I want, but I honestly
went hunting and couldn't find the stuff. So, sorry if this is a dumb question,
but this vt100 lock-up problem drives me nuts.
ie. PUT SIMPLY WHAT IS THE TERMINAL TYPE OF A DM WINDOW?????
SURELY PEOPLE RLOGIN INTO NON APOLLO SYSTEMS WITHOUT USING VT100
DON"T THEY?
-thanks
-dennis
--
--------------------------------------------------------------------------------
Dennis Vadura, Computer Science Dept., UUCP,BITNET: dvadura@water
University of Waterloo, Waterloo, Ont. EDU,CDN,CSNET: dvadura@waterloo
================================================================================weber_w@apollo.COM (Walt Weber) (02/24/89)
In article <11588@watdragon.waterloo.edu> dvadura@watdragon.waterloo.edu (Dennis Vadura) writes: >System: DN 3500 >OS: SR 10.1 [...stuff deleted...] >Anyway, after staring into the 3 feet of documentation we have on Apollos here >I see no mention of a termcap like capabilities description for DM windows. [...stuff deleted...] >ie. PUT SIMPLY WHAT IS THE TERMINAL TYPE OF A DM WINDOW????? Dennis : The DM does not have any command sequences which can be embedded in the output stream in order to control cursor positioning, display attributes, etc. This facility is offered through the vt100 emulator, as you already know. Why?? The display manager, in creating/displaying windows, can be thought of as mapping a portion of an underlying file into the display memory. It is NOT a terminal (or a pseudo-terminal), but a "view" of a portion of the underlying file. Responding to embedded control sequences to do "cursor positioning" under this model of operation would be similar to requiring that file pointer seeks be done by embedding escape sequences in write(2). Remember, BOTH are operating on files. Thus, you gain the "infinitely scrollable transcript pads", but don't have cursor positioning. Under the vt100 emulator, you get the ability to "clear screen", but give up the ability to reverse scroll the output window to the beginning of the session. Hope this helps. ...walt... -- Walt Weber Apollo Computer (508) 256-6600 x8315 People's Republic of Massachusetts -The views expressed herein are personal, and not necessarily Apollo's-
freedman@cpsc.ucalgary.ca (Dan Freedman) (02/26/89)
In article <41a7cf1a.1b0ea@apollo.COM> weber_w@apollo.COM (Walt Weber) writes: >The DM does not have any command sequences which can be embedded in the output >stream in order to control cursor positioning, display attributes, etc. [much deleted] >Thus, you gain the "infinitely scrollable transcript pads", but don't >have cursor positioning. It would be nice if the portion of the DM window that was visible would act like a vt100, and the portion that was off screen would act like a transcript. Note that if output occurs while the user is paged back somewhere in the transcript, the DM would then update that portion of the end of the transcript that *would* have been in the window wer the user not paging backward. Ie: the off screen part of the transcript is read-only, even when the user brings it on screen by paging backwards. Only the bottom n lines (where n is determined by the window size) of the transcript act like a vt100. This behaviour can be seen in Versaterm Pro (and possibly also the normal version of Versaterm) for the Apple Macintosh, and is very useful. There is no intrinsic reason why this combined functionality cannot be made available in the DM, other than it might require a fairly radical change in the DM's programming. Dan Freedman University of Calgary Computer Science Department 2500 University Drive N.W. freedman@cpsc.UCalgary.CA Calgary, Alberta, T2N 1N4 ...!alberta!calgary!freedman
conliffe@caen.engin.umich.edu (Darryl C. Conliffe) (03/01/89)
In article <802@cs-spool.calgary.UUCP>, freedman@cpsc.ucalgary.ca (Dan Freedman) writes: > > It would be nice if the portion of the DM window that was visible > would act like a vt100, and the portion that was off screen would > act like a transcript. Note that if output occurs while the user is You can use F8S as a toggle to control whether or not the VT100 emulator appends to the underlying transcript file any text scrolled off the top of the screen. See help vt100/keys. -- ___________________ Darryl C. Conliffe conliffe@caen.engin.umich.edu (313) 721-6069 -------------------
freedman@ksi.cpsc.UCalgary.CA (Dan Freedman) (03/03/89)
In article <41a7cf1a.1b0ea@apollo.COM> weber_w@apollo.COM (Walt Weber) writes: >The DM does not have any command sequences which can be embedded in the output >stream in order to control cursor positioning, display attributes, etc. [much deleted] >Thus, you gain the "infinitely scrollable transcript pads", but don't >have cursor positioning. It would be nice if the portion of the DM window that was visible would act like a vt100, and the portion that was off screen would act like a transcript. Note that if output occurs while the user is paged back somewhere in the transcript, the DM would then update that portion of the end of the transcript that *would* have been in the window wer the user not paging backward. Ie: the off screen part of the transcript is read-only, even when the user brings it on screen by paging backwards. Only the bottom n lines (where n is determined by the window size) of the transcript act like a vt100. This behaviour can be seen in Versaterm Pro (and possibly also the normal version of Versaterm) for the Apple Macintosh, and is very useful. There is no intrinsic reason why this combined functionality cannot be made available in the DM, other than it might require a fairly radical change in the DM's programming. Dan Freedman University of Calgary Computer Science Department 2500 University Drive N.W. freedman@cpsc.UCalgary.CA Calgary, Alberta, T2N 1N4 ...!alberta!calgary!freedman