Double CTRL-C in shell get you completely out

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Double CTRL-C in shell get you completely out

Tony Papadimitriou
Recently CTRL-C was improved to abort the query and stay in the CLI.  This is very good.

However, if (accidentally, e.g., key bounce) a second CTRL-C is entered, it will escape back to the console.

Could it be changed so that either:

1. Only CTRL-D (Linux) or CTRL-Z (Windows) is used to exit the CLI

-- or --

2. If doing CTRL-C at the CLI prompt when nothing’s running to first confirm (like ‘Are you sure?’ with a No default, so that an explicit ‘Y’ has to be entered)?

Thank you.
_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Reply | Threaded
Open this post in threaded view
|

Re: Double CTRL-C in shell get you completely out

Dominique Devienne
On Wed, Jul 31, 2019 at 8:37 PM Tony Papadimitriou <[hidden email]> wrote:

> Recently CTRL-C was improved to abort the query and stay in the CLI.  This
> is very good.
>

FWIW, SQliteSpy uses the escape key (ESC) to abort a run-away query (Hello
incorrect recursive CTE!)
I'd prefer CTRL-C to keep killing the current process, and ESC to abort
queries. My $0.02... --DD

PS: Avoids overloading the meaning of CTRL-C/D/Z with non-standard behavior.
_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users