Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!news.cac.psu.edu!news.cse.psu.edu!uwm.edu!lll-winken.llnl.gov!nntp.coast.net!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!in2.uu.net!news.u.washington.edu!raindrop!unger
From: unger@raindrop.seaslug.org (Thomas Unger)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: FreeBSD emacs oddness
Date: Sat, 4 May 1996 02:23:42 GMT
Organization: Wet Weather Consulting
Lines: 22
Message-ID: <DquzzJ.IEJ.0.raindrop.seaslug.org@raindrop.seaslug.org>
References: <4mcmd0$5uu@itchy.serv.net>
NNTP-Posting-Host: cs124-12.u.washington.edu
In article <4mcmd0$5uu@itchy.serv.net>, Sean T. Lamont <zeno@serv.net> wrote:
>I fetched the emacs package of wcarchive and installed it, but I've
>noticed that in some environments (most reproducibly under [t]rn), the
>^G ("cancel") tends to do the following:
>
>- it leaves emacs running in the foreground
>- it returns control to the parent process (??????)
I don't have a fix but I'll confirm that I've seen the same thing.
But only when you run emacs within the xterm window of the parent
process. Not the perfect solution but if you let emacs open it's own
window everything works.
Tom.