[jboss-jira] [JBoss JIRA] (WFCORE-2896) Revisit CLI Ctrl-C handling

Radoslav Husar (JIRA) issues at jboss.org
Thu Jun 1 08:06:00 EDT 2017


    [ https://issues.jboss.org/browse/WFCORE-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414918#comment-13414918 ] 

Radoslav Husar commented on WFCORE-2896:
----------------------------------------

Understood, another option to keep the existing behavior is to: (1) if something is typed and CTRL+C is pressed, discard and start a new line and (2) if the line is empty and CTRL+C is typed, then exit. It's not exactly what I would prefer, but still would be an improvement.

> Revisit CLI Ctrl-C handling
> ---------------------------
>
>                 Key: WFCORE-2896
>                 URL: https://issues.jboss.org/browse/WFCORE-2896
>             Project: WildFly Core
>          Issue Type: Enhancement
>          Components: CLI
>            Reporter: Jean-Francois Denise
>            Assignee: Jean-Francois Denise
>
> Ctrl-C typed in the CLI behaviour:
> - If auto-connect is enabled (-c option). If prompt occurs for credentials, typing Ctrl-C should exit the CLI process 
> - As soon as we have reached the CLI prompt, any prompting is bound to a command execution (eg: connect, reload, ...), in that case Ctrl-C shouldn't exit the process. It should interrupt the command
> - Ctrl-C typed for long running command should only interrupt the command.
> - Ctrl-C typed when pausing long output should only interrupt output pause.
> - Ctrl-C typed in the terminal without command running exit the CLI process.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jboss-jira mailing list