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

Spago run is confusing #292

justinwoo opened this issue Jun 25, 2019 · 3 comments


Copy link

commented Jun 25, 2019

$ spago run -h
Usage: spago run [-m|--main MAIN] [-j|--jobs JOBS]
                 [-c|--global-cache GLOBAL-CACHE] [-w|--watch]
                 [-l|--clear-screen] [-p|--path PATH] [-n|--no-install]
                 [ ..ANY `PURS COMPILE` OPTION] [-n|--node-args NODE-ARGS]
  Runs the project with some module, default Main

Available options:
  -m,--main MAIN           Module to be used as the application's entry point
  -j,--jobs JOBS           Limit the amount of jobs that can run concurrently
  -c,--global-cache GLOBAL-CACHE
                           Configure the global caching behaviour: skip it with
                           `skip` or force update with `update`
  -w,--watch               Watch for changes in local files and automatically
  -l,--clear-screen        Clear the screen on rebuild (watch mode only)
  -p,--path PATH           Source path to include
  -n,--no-install          Don't run the automatic installation of packages
                           Options passed through to `purs compile`; use -- to
  -n,--node-args NODE-ARGS Argument to pass to node (run/test only)
  -h,--help                Show this help text

-n appears twice, for no-install and node-args


This comment has been minimized.

Copy link

commented Jun 25, 2019

Oops 😄

@justinwoo any proposals for the new short names? Maybe -x for the --no-install?

@f-f f-f added the defect label Jun 25, 2019


This comment has been minimized.

Copy link

commented Jun 25, 2019

Maybe -N for --no-install?


This comment has been minimized.

Copy link

commented Jun 26, 2019

Oops, looks like the two PRs were in flight at the same time. -a for --node-args could make sense too. Glad to fix it with the winning alternative.

Also not sure how much you worry about breaking changes but at present --no-install is "winning" the fight for -n since it appears first, so switching --node-args is non-breaking. Just a thought.

@justinwoo justinwoo referenced this issue Jun 26, 2019
0 of 3 tasks complete

@f-f f-f closed this in #293 Jun 26, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
4 participants
You can’t perform that action at this time.