Path: utzoo!utgpu!attcan!uunet!ncrlnk!ncrcae!hubcap!gatech!ukma!rutgers!aramis.rutgers.edu!geneva.rutgers.edu!hedrick From: hedrick@geneva.rutgers.edu (Charles Hedrick) Newsgroups: comp.windows.news Subject: Grasshopper psterm Message-ID: Date: 10 Nov 88 02:34:47 GMT Organization: Rutgers Univ., New Brunswick, N.J. Lines: 29 I've been using the new psterm from the Grasshopper group since about 5 minutes after we got the posting. (I was desperate for a reasonable terminal emulator.) I appreciate the work, and I'm generally very pleased with the way it works. However I've got a few problems, and I'm curious whether anybody knows what's going on. First, it feels slow. I'm not all that concerned about how long NeWS takes to do complex operations. However when I type I'm very sensitive to echo delay. The old psterm and Gnu Emacs with NeWS support don't cause me any trouble, but the new psterm causes just enough echo delay to be annoying. Second, I have trouble exiting. With the old psterm, and all other NeWS programs, when I kill the program, the window goes away. With the new psterm, I can't get rid of the window. Neither exiting from the shell inside it, doing "zap" in the menu, nor killing the process helps. I can make "zap" work by modifying psterm.ps, but I still can't make it go away if I exit from the shell. The modification to make zap work is to add the two lines with /Mapped false below: /destroy { /Scrollbar null def IconCanvas /Mapped false put FrameCanvas /Mapped false put /destroy super send } def Finally, if I try it with retained windows disabled, results are a bit odd. As long as the window is on top, things work fine. But if it's occluded, I tend to have whole lines of text missing.