You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not a bug but it's annoying when we implement a command running an external agent from our CLI and keep running it until the user hit "Ctrl+C". On Windows, since oclif's batch scripts naively execute Node.js program, Ctrl+C always asks the user to terminate the job like below:
We implemented a patch for this solution. If you feel this is the right approach, we can send a PR with a flag or environmental variable for oclif pack tarball and oclif pack win to enable these new script optionally. We also need the similar one in @oclif/plugin-update.
The text was updated successfully, but these errors were encountered:
riywo
changed the title
[Feature request] New Windows batch script to handle Ctrl+C better
[Feature request] Windows batch scripts to handle Ctrl+C better
Sep 15, 2022
What is the current behavior?
Not a bug but it's annoying when we implement a command running an external agent from our CLI and keep running it until the user hit "Ctrl+C". On Windows, since oclif's batch scripts naively execute Node.js program, Ctrl+C always asks the user to terminate the job like below:
What is the expected behavior?
No confirmation like Linux or macOS.
We implemented a patch for this solution. If you feel this is the right approach, we can send a PR with a flag or environmental variable for
oclif pack tarball
andoclif pack win
to enable these new script optionally. We also need the similar one in@oclif/plugin-update
.Patches:
https://github.com/autifyhq/autify-cli/blob/12e2191aa93ae04a640153b651dd92ba8b1429d6/patches/oclif%2B3.2.28.patch
https://github.com/autifyhq/autify-cli/blob/12e2191aa93ae04a640153b651dd92ba8b1429d6/patches/%40oclif%2Bplugin-update%2B3.0.7.patch
The text was updated successfully, but these errors were encountered: