Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!unicorn!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: <11354@ogicse.ogi.edu>
Date: 15 Aug 90 00:52:52 GMT
References: <1990Aug14.172947.27179@jts.com>
Organization: Oregon Graduate Institute (formerly OGC), Beaverton, OR
Lines: 17

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