Re: Should `dub run` prints its output to STDERR?

2017-09-09 Thread Martin Tschierschke via Digitalmars-d-learn
On Saturday, 9 September 2017 at 05:58:59 UTC, Ali Çehreli wrote: On 09/08/2017 09:51 PM, Ky-Anh Huynh wrote: > When I execute a program thanks to dub, `dub` also prints its > information to STDOUT: Try dub's --quiet command line switch. Ali Can I configure this also in dub.json (dub.sdl)?

Re: Should `dub run` prints its output to STDERR?

2017-09-09 Thread Ky-Anh Huynh via Digitalmars-d-learn
On Saturday, 9 September 2017 at 05:58:59 UTC, Ali Çehreli wrote: On 09/08/2017 09:51 PM, Ky-Anh Huynh wrote: > When I execute a program thanks to dub, `dub` also prints its > information to STDOUT: Try dub's --quiet command line switch. Ali That's perfect. Thanks a lot.

Re: Should `dub run` prints its output to STDERR?

2017-09-09 Thread Ali Çehreli via Digitalmars-d-learn
On 09/08/2017 09:51 PM, Ky-Anh Huynh wrote: > When I execute a program thanks to dub, `dub` also prints its > information to STDOUT: Try dub's --quiet command line switch. Ali

Should `dub run` prints its output to STDERR?

2017-09-08 Thread Ky-Anh Huynh via Digitalmars-d-learn
When I execute a program thanks to dub, `dub` also prints its information to STDOUT: [code] $ dub run dusybox:jq -- .status " 1" < /home/pi/df/acces.log |head -10 Building package dusybox:jq in /home/pi/projects/icy/dusybox/ Performing "debug" build using dmd for x86_64. dusybox:jq