Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ammonite should be interruptible when it is not used interactively #224

Closed
patrick-premont opened this issue Sep 10, 2015 · 2 comments
Closed

Comments

@patrick-premont
Copy link

Ammonite captures control-c and #214 suggests capturing control-z. This is useful when using ammonite interactively as a shell. However this becomes a liability when working non-interactively.

I am unsure if using --code or passing in a parameter currently disables the capture of control-c. But #223 seems to suggest that control-c is captured even when input is redirected. If that is the desired behavior, perhaps we need a command-line flag to explicitly disable the capture of control-c ?

@lihaoyi
Copy link
Member

lihaoyi commented Sep 13, 2015

We probably should disable all the signal capturing rubbish when not run interactively, e.g. through running script files or running with -c

@lihaoyi
Copy link
Member

lihaoyi commented Nov 16, 2015

Should be fixed by #242 I think

@lihaoyi lihaoyi closed this as completed Nov 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants