Path: utzoo!attcan!uunet!husc6!bbn!rochester!pt.cs.cmu.edu!andrew.cmu.edu!mp1u+ From: mp1u+@andrew.cmu.edu (Michael Portuesi) Newsgroups: comp.sys.amiga Subject: Re: Dmouse and PATH (was Re: POPcli bug? (was Re: ConMan Question)) Message-ID: Date: 2 Jul 88 02:54:35 GMT References: <1357@tahoe.unr.edu> <6558@jhunix.HCF.JHU.EDU> <2002@ihlpm.ATT.COM>, <90jTD94ep11010ZOynU@amdahl.uts.amdahl.com> Organization: Carnegie Mellon Lines: 32 In-Reply-To: <90jTD94ep11010ZOynU@amdahl.uts.amdahl.com> > *Excerpts from ext.nn.comp.sys.amiga: 27-Jun-88 Re: POPcli bug? (was Re:* > *Co.. Kim DeVaughn@amdahl.uts. (1635)* [about Dmouse CLI's not inheriting the correct PATH] > Or maybe try compiling DMouse with the alternate startup code that Carolyn > (I think) posted. Or just bite the bullet and put the "path" command in > your "from" file. I'd suggest adding a "cd" command to the dir you want to > be in, up at the top of the "from" file also (see previous followup for why). That is a totally unacceptable solution. I have only one disk drive, and REZ a batch of commands so that I don't have to keep my startup disk around all the time. One of those commands is "newcli". If I am forced to use a "from" file to get the PATH set correctly, I will have to swap disks every time I want a new CLI. Perhaps Matt could possibly fix this problem in 1.08? One very tiny problem with Dmouse 1.07: The pointer is automatically blanked when the screen is blanked irregardless of whether or not mouse blanking is enabled. However, when mouse blanking is disabled, the mouse pointer does not reactivate along with the display on a keypress. It does reactivate with the display on a mouse movement. --M Michael Portuesi / Information Technology Center / Carnegie Mellon University ARPA/UUCP: mp1u+@andrew.cmu.edu BITNET: rainwalker@drycas "if you ain't ill it'll fix your car"