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

Messages about compiling files should go to stderr rather than stdout #574

Closed
nessus42 opened this Issue Mar 9, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@nessus42

nessus42 commented Mar 9, 2017

Ammonite messages about compiling files should go to stderr rather than stdout.

Yes, I know I can silence such output with "-s", but sometimes it is useful to see such output (so, e.g., I know why the script is running slowly), without having it ruin the contents of the output file when you run a script like so:

$ amm foo.sc > output.txt

The Ivy output currently all goes to stderr (which is where it should go), so having the compiling messages go to the same place would also be more consistent.

@DavidPerezIngeniero

This comment has been minimized.

DavidPerezIngeniero commented Mar 10, 2017

+1

@lihaoyi

This comment has been minimized.

Owner

lihaoyi commented Mar 10, 2017

Yeah that's a great idea.

lihaoyi added a commit that referenced this issue May 12, 2017

Fix crash when running an empty script
This came up when investigating #574. It's not the original problem
being reported, but it was an easy ix

@lihaoyi lihaoyi closed this in 6ff30c9 May 12, 2017

jhnsmth added a commit to jhnsmth/Ammonite that referenced this issue May 21, 2017

Fix crash when running an empty script
This came up when investigating lihaoyi#574. It's not the original problem
being reported, but it was an easy ix

jhnsmth added a commit to jhnsmth/Ammonite that referenced this issue May 21, 2017

Fix lihaoyi#574 by making info messages go to stderr rather than stdout
- Split out the `infoStream` from the `errorStream`, though both go to
  stderr by default, in case people want to redirect them

- More consistently use `Printer#info` instead of `Printer#out` for misc
  logging information

- `--silent` flag now simply shuts off all `info` logging, rather than
  doing different clever things in each subsystem
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment