Path: utzoo!attcan!uunet!snorkelwacker!apple!usc!chaph.usc.edu!phakt.usc.edu!tli From: tli@phakt.usc.edu (Tony Li) Newsgroups: comp.unix.internals Subject: Re: RAM disk. Message-ID: <12454@chaph.usc.edu> Date: 11 Oct 90 19:23:12 GMT References: <14884@hydra.gatech.EDU> Sender: news@chaph.usc.edu Organization: University of Southern California, Los Angeles, CA Lines: 19 Nntp-Posting-Host: phakt.usc.edu In article <14884@hydra.gatech.EDU> gt0178a@prism.gatech.EDU (Jim Burns) writes: Wrong - unless you are using a windowing environment, and there are still plenty of glass tube unices out there. And even then, few windowing environments I've worked in can match the one or two keystroke responsive - ness of a good TSR. (Granted, what you're talking about *does* apply to the filter and os extension types of TSRs.) This could be easily satisfied by implementing a different user interface to job control. Or even by programmable function keys. For example, you might bind one key to be: "^Z%emacs". Poof. The difficulty is doing this in a consistent and portable way... -- Tony Li - USC Computer Science Department Internet: tli@usc.edu Uucp: usc!tli Thus spake the master programmer: "A well written program is its own heaven; a poorly-written program its own hell."