Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!uwm.edu!ogicse!schaefer
From: schaefer@ogicse.ogi.edu (Barton E. Schaefer)
Newsgroups: comp.mail.mush
Subject: Re: Save command operation while in tool mode
Message-ID: <11452@ogicse.ogi.edu>
Date: 17 Aug 90 03:55:12 GMT
References: <1990Aug14.172947.27179@jts.com> <11354@ogicse.ogi.edu> <140702@sun.Eng.Sun.COM> <1990Aug16.191755.2891@jts.com>
Organization: Oregon Graduate Institute (formerly OGC), Beaverton, OR
Lines: 21

In article <1990Aug16.191755.2891@jts.com> gerry@jts.com (Gerry Roderick Singleton ) writes:
} In article <140702@sun.Eng.Sun.COM> argv@turnpike.Eng.Sun.COM (Dan Heller) writes:
} }> In article <1990Aug14.172947.27179@jts.com> gerry@jtsv16.jts.com (Gerry Roderick Singleton ) writes:
} }> } How can one configure .mushrc so that mushtool will refrain from asking
} }> } confirmation for every save request?
} }
} }Something else that frequently happens is that sys-admins set verify in
} }the global Mushrc they install as the default config file.
} 
} I was operating under the assumption commands in the local .mushrc
} override those in the system Mushrc.  I will correct immediately.

Just so nobody gets any more confused than they probably already are:

Commands in the local .mushrc *_DO_* override those in the system Mushrc.

However, $verify picked up the ability to control confirmation for save
requests in patch #2.  If the version displayed at the top of your mush
window is not 7.1.2, you can't stop mush from asking for confirmation.
-- 
Bart Schaefer						schaefer@cse.ogi.edu