On Thu, 21 Jun 2001 [EMAIL PROTECTED] wrote:
> I should point out, that from looking through my copy of the mail
> archives, this is now the third or fourth time that -X has been brought
> up. The reason I am against this, is that I brought it up every other
> time, and we always decided against doing the work, or at least the work
> was never done, for one reason or another. I am sick of re-visiting the
> same issues over and over and over again. We have had this discussion far
> too often to be changing our minds yet again.
> > (AFAICT, it's not currently documented... may be wrong about that).
>
> It's documented in manual/upgrading.html
That's fine. Can we at least compromise as has been suggested and put
this issue to rest by documenting it in other places as well? I don't
think the issue would come up so often if people could easily figure out
how to get into the -X style debugging mode. It's only when you can't
figure it out and can't find the information on how to do it that you get
frustrated and bring up the issue on the list. Can we either have -X
return a hint and then exit() or let a help screen do the trick? Or
something? I'm not as attached to -X doing the deed as I am to being able
to quickly figure out that -DONE_PROCESS is what you should use.
<shrug>
--Cliff
--------------------------------------------------------------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
