Path: utzoo!utgpu!attcan!uunet!husc6!uwvax!rutgers!bellcore!jcricket!sjs From: sjs@jcricket.ctt.bellcore.com (Stan Switzer) Newsgroups: comp.windows.news Subject: Re: Grasshopper psterm Message-ID: <11641@bellcore.bellcore.com> Date: 10 Nov 88 14:25:57 GMT References: Sender: news@bellcore.bellcore.com Reply-To: sjs@ctt.bellcore.com (Stan Switzer) Organization: Bellcore Lines: 45 hedrick@geneva.rutgers.edu (Charles Hedrick) writes: > 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. I don't exactly like to look a gift horse in the mouth, but I'd have to agree. Don't take this too hard Grasshopper, but the extended psterm isn't really any closer to "production quality" than the original was. True, the new features are nifty, but it's still rough around the edges. > .... 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 I STRONGLY recommend against this. It cures the symptom but not the disease. If the canvas stays visible it is because some reference remains, and if, as you said later, the canvas is retained, then there is a good bit of memory tied up in that canvas--especially in color. Unless you actually lose every reference, you are just hiding a massive memory leakage. Probably there is a reference loop among the dictionaries used in the program. I'd whip out Don's Hopkins' amazing "Pseudo-Scientific Visualizer" (the class browser for the other half of your brain) to debug this one if I were you. But I'm not -- I have other fish to fry. Oh, and while I'm at it, here's one more person who'd LOVE to have someone from Adobe post a technical summary of the new features in Display Postscript. I mean, unless you post some actual information, you are just as bad as the Eiffel partisans sniping in the C++ newsgroup. (Too bad, too, Eiffel is a decent language, though you'd never know it from the postings.) You guys at Adobe do good work -- let us in on it. Stan Switzer sjs@ctt.bellcore.com "A verb, Senator Kennedy, we need a verb!"