Cannot call @system funciton (stdout)
zorael at gmail.com
Sat Sep 19 15:56:37 UTC 2020
On Saturday, 19 September 2020 at 14:14:46 UTC, Paul Backus wrote:
> You can check the TERM environment variable , or you can use
> the POSIX uname() function  to see if you're running under
> Cygwin specifically. If there are any other environments where
> you need to manually set line-buffering, you'll probably have
> to check for those individually as well.
All right, thanks. Yes, currently I'm doing the TERM and uname
thing on program start and flushing manually after every writeln
if I detected Cygwin or vscode.
I think I can work with this.
More information about the Digitalmars-d-learn