Exit Command [E/F8]
Exit from Qedit and return to the operating system.
EXIT [string]
The current workfile is closed and Qedit terminates. The F8 user key is the same as Exit.
To close the current workfile without exiting, use Shut. Remember: you do not need to Exit in order to do :COBOL, rep or :Run, but you do need to Exit in order to do :BYE.
When you Exit, Qedit checks whether you have any unsaved edits in any of your Extra scratch files. If so, you are prompted to Discard? them, or stay in Qedit to save them. If your primary Qeditscr file is temporary and named “Qeditscr”, Qedit warns you that you forgot to save your changes, but does not purge the file. You can re-enter Qedit, Open it and resume work or save your edits.
Examples
:hello bob.green {log on to the computer} :run qedit.pub.robelle /open qedit.doc {open file to work on} /modify 2482.5/ {do some editing...} . . . /:prose * {use a UDC to format a document} /exit {ready to quit for the day!} :bye {disconnect from computer}
Notes
To avoid accidental Exit as a result of pressing F8 one time too many, you can run Qedit with Parm=64. This forces user approval of Exit.
The only situation where Qedit does not terminate on an Exit is when you invoke Qedit from another user program (e.g., from SPOOK, MPEX, or SELECT). In this case, Qedit “suspends” so that the father process can quickly “activate” Qedit again. When you reactivate Qedit you can resume editing with Open *. If the father does not want to hold onto Qedit, he should get rid of it with the KILL intrinsic. If the father process is like HPDesk and does not notice that Qedit remains suspended, you should :Run Qedit with Parm=32 or do Set Suspend Off to force Qedit to terminate on Exit instead of suspending.
The string parameter is only allowed when Qedit is running as a server. The string is a message sent to the Qedit for Windows client. The client receives the exit notification, displays the message and disconnects immediately. If no string is specified, a default message is displayed.