Messages about compiling files should go to stderr rather than stdout #574
Comments
|
+1 |
|
Yeah that's a great idea. |
lihaoyi
added a commit
that referenced
this issue
May 12, 2017
This came up when investigating #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
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
- 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
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:
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.
The text was updated successfully, but these errors were encountered: