gerry@jtsv16.jts.com (Gerry Roderick Singleton ) (08/15/90)
I certain this question was answered a short while ago but I find no
record in my archives. So here's the question again:
How can one configure .mushrc so that mushtool will refrain from asking
confirmation for every save request? Some background, verify is off.
What I like to do is read my messages and save each to the appropriate
folder. Mushtool won't perform in a manner consistant with my
requirements for saving which are, simply stated, "DO IT and BE QUIET."
One more thing. Is there an easy way to have mush skip to the next
unread message after a save? I'd like this feature too.
ger
--
--
G. Roderick Singleton, System and Network Administrator, JTS Computers
{uunet | geac | torsqnt}!gerry@jtsv16.jts.comschaefer@ogicse.ogi.edu (Barton E. Schaefer) (08/15/90)
In article <1990Aug14.172947.27179@jts.com> gerry@jtsv16.jts.com (Gerry Roderick Singleton ) writes: } I certain this question was answered a short while ago but I find no } record in my archives. So here's the question again: } } 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? } One more thing. Is there an easy way to have mush skip to the next } unread message after a save? I'd like this feature too. There currently is no way to have this happen automatically. -- Bart Schaefer schaefer@cse.ogi.edu
argv@turnpike.Eng.Sun.COM (Dan Heller) (08/16/90)
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.
gerry@jts.com (Gerry Roderick Singleton ) (08/17/90)
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
schaefer@ogicse.ogi.edu (Barton E. Schaefer) (08/17/90)
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