Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!usc!apple!sun-barr!newstop!sun!argv
From: argv@turnpike.Eng.Sun.COM (Dan Heller)
Newsgroups: comp.mail.mush
Subject: Re: Save command operation while in tool mode
Message-ID: <140702@sun.Eng.Sun.COM>
Date: 15 Aug 90 19:13:12 GMT
References: <1990Aug14.172947.27179@jts.com> <11354@ogicse.ogi.edu>
Sender: news@sun.Eng.Sun.COM
Organization: O'Reilly && Associates
Lines: 20

In article <11354@ogicse.ogi.edu> schaefer@ogicse.ogi.edu (Barton E. Schaefer) 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?  Some background, verify is off.
> Unless you are trying to save a deleted message, you should be queried
> only if $verify contains the string "save".  What version does your mush
> claim to be?  Do you have any lines like "cmd save  ..." in .mushrc?

Something else that frequently happens is that sys-admins set verify in
the global Mushrc they install as the default config file.  I've been
seeing this happen more frequently as mush becomes installed on a site-wide
basis.  You should check to see that it has been completely unset
(it sounds like you are, but the mistake is common enough that I
felt like mentioning it anyway).

--
dan
----------------------------------------------------
O'Reilly && Associates   argv@sun.com / argv@ora.com
Opinions expressed reflect those of the author only.