#: 7855 S15/Hot Topics
    28-Oct-90  18:15:01
Sb: #7673-#OSK Software
Fm: Jay Truesdale 72176,3565
To: Frank Hogg 70310,317 (X)

Frank:

I like the idea of the C/C.  Seems to me that it would be in everyone's best
interest to have some two way communication with Microware so that we don't set
up a 'standard' only to have Microware release some new product that would
supercede the user developed standard.

I'd like to see a standard created for a means of associating a hardware port
with with the type of terminal attached.  For example, say I have a Televideo
925 on port /t1 and a DEC VT-100 on port /t2 and I normally log on to port
 /t1.  In my ".login" file I set the environment variable TERM to 925.
Microware's mail & uMacs now work great.  My terminal is being used by someone
so I go and log on to the VT-100 on /t2, my TERM environment variable is still
(incorrectly) set to the 925 and any software that uses the TERM environment
variable doesn't work so well any more.  The termcap method seems to assume
that a shop has only one make and model of terminal and/or that a user only
logs on to one terminal and/or that you wouldn't have two people working in the
same directory on different types of terminals.  On my system at work I have
THREE different sets of terminal definition files for three different software
packages (Quick ED, Sculptor, and Mail).  What a waste of disk space and
effort!  A standard file in a standard place with the association between ports
and terminal types would be a big help.

I wrote Microware a letter about this but they never bothered to answer.

-J

There are 3 Replies.