ellis@flairvax.UUCP (Michael Ellis) (07/27/83)
We have a number of Gosling Emacs problems the occur on our 4.1(a)bsd system. Some of these have known fixes that I can't locate; others may go away whenever we get 4.2 and its Emacs upgrades (I'd still like such fixes 'til then). Does anybody know about these ? 1. The multiple EMACS invocation fix to the kernel. Manifests itself when you `fg' to the earlier of 2 stopped invocations. Result is an unkillable zombie EMACS. 2. Ann Arbor Ambassador screen `pessimization' that tries to save time re-using characters on the screen where not appropriate. Very obnoxious at 1200 baud when trailing `;'-s or `)'-s recur in the edited file. The code has that notorious skull-and-crossbones!! 3. Occasional random lost edits when `fg'-ing to a stopped EMACS, this time dying with the message: Infinite tc=loop No environment-specified terminal type--see TSET(1) 4. Garbage hanging around in the minibuf (bottom line). Usually the junk is remains from an aborted M-x command. A symptom of cancerous brain-damage ultimately resulting in complete loss of the edit session. Nonetheless, I am a Gosling Emacs fanatic to the end... Michael Ellis - Fairchild AI Lab - Palo Alto CA - (415) 858-7250