Control-c in sqlplus on Windows leaves me at C: prompt

Question

An annoying "feature" of the command line version of SQL*Plus (sqlplus.exe not sqlplusw.exe) is that a control-c will cause the program to abort.
If I set pause on and want to break out of the execution of the query, i end up aborting my sqlplus session.
On unix, a control-c (break) will simply abort the current command, not the program.
Does anyone know a windows work-around or setting to avoid this program exiting "feature".

Answer 1

user12286392 wrote:
An annoying "feature" of the command line version of SQL*Plus (sqlplus.exe not sqlplusw.exe) is that a control-c will cause the program to abort.
If I set pause on and want to break out of the execution of the query, i end up aborting my sqlplus session.
On unix, a control-c (break) will simply abort the current command, not the program.
Does anyone know a windows work-around or setting to avoid this program exiting "feature".Ctrl-C during a query execution should take it back to the SQL> prompt, whilst Ctrl-C at the SQL> prompt will cause sqlplus to exit back to the cmd prompt. This is standard levels of execution and termination for processes and has always worked like this for any process written. It is up to the process itself to capture ctrl-C and handle it as it sees fit, and most processes at the top level of their "business process" (for want of a better way of putting it) will capture it and exit the process. Likewise in unix environments processes run in similar ways with Ctrl-Z stopping jobs except that they can then be killed or put into the background or brought back to the foreground.
In truth it does exactly what I would expect it to do. It's not an unusual "feature", it's the way these operating systems and processes have always worked over the decades. So, I would say, stop hitting Ctrl-C unless you are doing it for a reason.