Path: utzoo!utgpu!news-server.csri.toronto.edu!torsqnt!lethe!geac!jtsv16!gerry
From: gerry@jts.com (Gerry Roderick Singleton )
Newsgroups: comp.mail.mush
Subject: Re: Save command operation while in tool mode
Message-ID: <1990Aug16.191755.2891@jts.com>
Date: 16 Aug 90 19:17:55 GMT
References: <1990Aug14.172947.27179@jts.com> <11354@ogicse.ogi.edu> <140702@sun.Eng.Sun.COM>
Organization: JTS Computer Systems Ltd.
Lines: 31

In article <140702@sun.Eng.Sun.COM> argv@turnpike.Eng.Sun.COM (Dan Heller) writes:
}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

BINGO!  I just sent Bart a pile of data for analyis ( Bart if your're 
listening, just turf it) in hopes of discovering the solution.  Well there
it is.  I was operating under the assumption commands in the local .mushrc
override those in the system Mushrc.  I will correct immediately.

Thanks guys,

ger
-- 
--
G. Roderick Singleton, System and Network Administrator, JTS Computers 
	{uunet | geac | torsqnt}!gerry@jtsv16.jts.com