-
Notifications
You must be signed in to change notification settings - Fork 31
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
Add colour output #25
Comments
@Sebastian-Brzuzek, could you give this a go on a windows machine and pull and merge if ok? |
@landro I just executed tests and examples on WinXP and have a lot of errors like this one:
I'm not sure if my environment is setup in correct way, so I will try to test it on Win7 in the evening and let you know if it is the same. I have no time Today to try to fix it, but I will try to look on it during next days. |
@Sebastian-Brzuzek It might be related to the disabled exec command. I enabled it again to make this work. Make sure you have a clean repo - maybe the easiest is to check out the coloured_messages branch |
@landro I was testing on clean check out of the coloured_messages branch, so this is not related to disabled exec command (I was using jtcl to be sure there is no problem with tcl interpreter). |
@landro I just executed test.cmd on Win7 - result shared here https://gist.github.com/Sebastian-Brzuzek/7878312 |
@Sebastian-Brzuzek Oh man, totally forgot about updating and running these tests. Should be ok now. Would you mind retesting it quick? |
@landro now it looks much better. There are no errors. Your assumption about lack of colours in windows command line is correct as well. I will merge this branch to main in spare time today |
Hi, Please wait a little before you merge. I'll send a pull request when ready. Stefan Sendt fra min iPhone
|
OK. Let me know when there will be final version available (I will try to find the reason of problem on WinXP in the mean time, but we should not wait if it will be difficult to fix on this obsolete platform). Seba. |
I found there was incorrect setup of TCLLIBPATH in my WinXP environment pointing to some obsolete version of TesTcl. After cleanup of this environment varialble it looks even on WinXP everything works as expected - both tests.cmd and examples.cmd passed without errors. Cheers, |
green ok
red failed
The text was updated successfully, but these errors were encountered: