Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!swrinde!mips!pacbell.com!tandem!zorch!xanthian From: xanthian@zorch.SF-Bay.ORG (Kent Paul Dolan) Newsgroups: comp.sys.amiga Subject: Re: GNU Emacs ... 0.3! Message-ID: <1990Sep12.061711.25294@zorch.SF-Bay.ORG> Date: 12 Sep 90 06:17:11 GMT References: <1990Sep7.164514.19481@watcgl.waterloo.edu> <1990Sep9.174939.16737@zorch.SF-Bay.ORG> <1990Sep12.013443.10907@csun.edu> Distribution: comp Organization: SF Bay Public-Access Unix Lines: 30 bcphyagi@Twg-S5.uucp (Stephen Walton) writes: >xanthian@zorch.SF-Bay.ORG (Kent Paul Dolan) writes: >>[Can you] spawn all other jobs from within GNUemacs and capture the >>output into edit buffers as needed)? > >Unfortunately, the porter says in the latest README that he doesn't >have code yet to do this. Thanks. Probably wasn't the most sensible question in the world anyway. That was an important advantage of GNUemacs on a text only monitor with one window into the system. On the Amiga, as long as I "run" GNUemacs, I can do most of the same thing by pushing the window back and exposing a Shell window (though that doesn't capture output to the CLI into a buffer for me). It _would_ be handy if the window for GNUemacs resized nicely, at least. Then one could fire it up, push it out of the way, and pull it open again as needed (iconification would work nicely too). Both ways you get the "run all day" advantage with only one startup time to pay, even if it _is_ 3 minutes, if you have the memory to spare. Sorry for the muddled viewpoint in my prior question. Kent, the man from xanth. -- "Don't post when your tired, Kent." "But I'm _always_ tired." "That's because you're _always_ posting."