×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Fri, Dec 22, 2017 at 1:33 PM, Rob Berendt <rob@xxxxxxxxx> wrote:
I am NOT talking about changing command defaults but used in
just the right application. And you're right, it could have just as
easily been done with CLRSAVF first, and not one person would have raised
an eyebrow over "arbitrarily clearing a savf".
Rob, calm down. If you stop assuming everyone who doesn't immediately
agree with you is wrong, or unjustified, or has worse ideas than you,
or has no common sense, or whatever, you might have a chance of
recognizing that nobody is really going against your *actual*
suggestion.
People are simply against changing the command default. That's it. The
only reason anyone even thought it was worth commenting was that they
thought that is what you were proposing. (That's certainly what it
sounded like to me when I read your post that started this thread.)
Nobody is against *explicitly* using the CLEAR parameter, any more
than they are against using CLRSAVF first. (To be clear, there could
be some folks who *are* also against CLRSAVF for some reason, but for
those people, there would be no logical contradiction in being against
CLEAR(*REPLACE) as well.)
I honestly don't think anyone is clamoring for an interactive "are you
sure" kind of prompt.
John Y.
midrange.com
