Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!inquo!in-news.erinet.com!imci5!imci4!newsfeed.internetmci.com!news.ac.net!news.serv.net!not-for-mail From: zeno@serv.net (Sean T. Lamont) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: FreeBSD emacs oddness Date: 5 May 1996 02:22:19 -0700 Organization: ServNet Internet Services, Seattle, WA Lines: 21 Message-ID: <4mhs0b$dmi@itchy.serv.net> References: <4mcmd0$5uu@itchy.serv.net> <DquzzJ.IEJ.0.raindrop.seaslug.org@raindrop.seaslug.org> NNTP-Posting-Host: itchy.serv.net In article <DquzzJ.IEJ.0.raindrop.seaslug.org@raindrop.seaslug.org>, Thomas Unger <unger@raindrop.seaslug.org> wrote: >In article <4mcmd0$5uu@itchy.serv.net>, Sean T. Lamont <me> wrote >>- 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. Thanks. Unfortunately, this doesn't work too well for dialup shell! -- Sean T. Lamont, President / CEO, Abstract Software (ServNet) - Internet access * WWW hosting * TCP/IP * UNIX * NEXTSTEP * WWW Development - email: lamont@abstractsoft.com WWW: http://www.serv.net "...There's no moral, it's just a lot of stuff that happens". - H. Simpson