Re: [sqlite] Double CTRL-C in shell get you completely out
On Wed, Jul 31, 2019 at 8:37 PM Tony Papadimitriou 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 sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] Double CTRL-C in shell get you completely out
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 sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
