James,
thanks for your kind reply. But, the way I am using dofiles is that I
want to run the dofile, check the output, maybe try out a few commands
to check whether everything worked out the way I wanted it to be, and
then quit the program by a single click or by pressing the famous
ALT-F4 shortcut.
To my last point. How would you do it under UNIX or anything derived
from that OS? Do you identity whether a stata instance is running and
than force that process to take the dofile as a new argument? I have
some problems to imagine how one would achieve such behaviour. Anyway,
I would be delighted to get to know more about this.
Kind regards,
sebastian
On 8/27/05, James Muller <[email protected]> wrote:
> Have you read the help on exit?
>
> . help exit
>
> May be missing something, but don't you just want to end te do file with
> the line
>
> . exit, clear STATA
>
> If you want this to be optional you could begin your do file with
>
> . args force_exit
>
> and finish it with
>
> . if ("`force_exit'" != "") exit, clear STATA
>
> Then call your do file with the command
>
> > stata do mydofile.do force_exit
>
> or whatever is equivalent on Windows.
>
>
> From your last point (and the way you're using do files) it sounds like
> you'd enjoy unix/linux/etc. There is probably a simple way to check for
> processes using the Windows OS, but I'm not a Windows person so maybe not.
>
> James
>
>
>
>
> Seb Buechte wrote:
>
> >Hello everybody!
> >
> >I raised this issue once before and still, I would really appreciate
> >the possibility to "convince" Stata to let me quit the program without
> >confirmation that "I really want to do this, eventhough my data has
> >changed..."
> >
> >I am using Stata with an external editor to write (I dare to say "to
> >program") my dofiles. I have managed to run the dofile from inside
> >this editor by calling the Stata environment. Each time I invoke Stata
> >to run my dofile, Stata will create a new instance. That is fine for
> >me, but what bothers me is that I cannot turn off that
> >confirmation-message-box which will appear each time I want to close
> >that Stata instance that holds changed data. I wonder wether there is
> >a hidden feature which could be activated to keep Stata of requiring
> >that confirmation. If no such thing should exist, why not adding it?
> >The default could still be the "paranoid"-mode to prevent users of
> >loosing their created data. But for all those who feel like they know
> >what they are doing it would be great to be able to turn such mode off
> >- at least it would be for me...
> >
> >Another idea that just came across my mind is that it would be also
> >very nice to have a command line option for the wsestata-binary that
> >would check wether Stata is already running and if so to have the
> >dofile executed within the last Stata instance started. I know this
> >goes out to Statacorp's programmers. Still, why not asking for it?
> >
> >Thank you for considering this :)
> >
> >Sebastian
> >
> >
> >
> >
> *
> * For searches and help try:
> * http://www.stata.com/support/faqs/res/findit.html
> * http://www.stata.com/support/statalist/faq
> * http://www.ats.ucla.edu/stat/stata/
>
--
- Seb F Buechte
-
- Stay tuned!
*
* For searches and help try:
* http://www.stata.com/support/faqs/res/findit.html
* http://www.stata.com/support/statalist/faq
* http://www.ats.ucla.edu/stat/stata/
