Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cs.utexas.edu!usc!elroy.jpl.nasa.gov!ncar!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!nuchat!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.misc Subject: Re: TYpeahead implementations (Re: How do we change the scheduler? (Was Re: Multitasking at home...)) Message-ID: <7706@sugar.hackercorp.com> Date: 4 Feb 91 23:28:42 GMT References: <10640.tnews@templar.actrix.gen.nz> <7643@sugar.hackercorp.com> <10856.tnews@templar.actrix.gen.nz> Organization: Sugar Land Unix -- Houston, TX Lines: 32 In article <10856.tnews@templar.actrix.gen.nz> jbickers@templar.actrix.gen.nz (John Bickers) writes: > Suppose I start MicroEMACS from > a WShell, and while it is loading from my slow HD I hit M-G124 to > go to line 124... under MS-DOS these keystrokes go to MicroEMACS. Unless MicroEmacs opens a window of its own under DesqView or Microsoft Windows. > On the Amiga, they go to WShell. Only if you have a crummy version of MicroEmacs like the one Commodore distributes that opens its own window. > On a single-tasking system, the > input is much more likely to behave in an unshared way like MS-DOS, > which is the basis of my statement above. You mean like on the Macintosh? > Under programs that > continued to take input from the console they were started from (ie: > stayed within a single task), you'd be correct. Very few programs > I use do this. They all stay in the same task. This has, for the second time, nothing to do with multitasking. Nothing. Nada. Zip. Zero. In fact Emacs *is* still running in the shell you started from, and you can't give *it* any more commands until Emacs finishes. -- Peter da Silva. `-_-' .