nigel@cmsfl@labtam.oz (nigel) (12/29/89)
Running csh on a Tower 32/600 under 1.03.02 I have problems with newgrp. The problem in a nut|sea shell is that after I have done a newgrp I lose the history capability of csh. Now I don't mean the history from my previous shell i.e. what I did before the newgrp as this will obviously be lost. What I mean is that after the newgrp the history does not work at all. I struck this problem a long time ago and will take advantage of the new comp.sys.ncr group to see if anyone has come up with a workaround. -- <<<<<<<<<<<<<<<<<<<<<<< Nigel Harwood >>>>>>>>>>>>>>>>>>>>>>>>> << Post: Coles Myer Ltd, PO Box 2000 Tooronga 3146, Australia >> << Phone: +61 3 829 6090 E-mail: nigel%cmsfl@labtam.oz.au >> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
wescott@Columbia.NCR.COM (Mike Wescott) (01/04/90)
In article <319@cmsfl> nigel@cmsfl@labtam.oz (nigel) writes: > The problem in a nut|sea shell is that after I have done a newgrp > I lose the history capability of csh. Yep. Bug in csh, for some reason it doesn't think that it is a login shell any more. I don't see any good reason why it should happen this way. Try: exec csh -i as a work around. And complain to your local NCR people to get a problem report submitted on it. -- -Mike Wescott mike.wescott@ncrcae.Columbia.NCR.COM