-
Notifications
You must be signed in to change notification settings - Fork 42
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
Strange output on Windows #24
Comments
Strange... Which version of Windows are you using? And which version of PyGitUp? |
I'm using Windows 7 (x64, Service Pack 1), with Python 2.7.8. GitUp is at version v1.3.0. |
Same Problem
|
I can now reproduce this behaviour. Will investigate... |
Looks like it's a regression of some kind in colorama introduced in tartley/colorama@961428e. I'm not sure what the right fix is here (besides downgrading the dependency). Could you both run |
For now we'll have to live with a workaround. Could you try the latest dev version ( |
It seems like it's still the same for me with dev version, also I suggest to add an option to disable coloring entirely since it would be useful not only in that case but to help users annoyed by colors 😄 |
Okay, this is getting really interesting. For reference, the latest dev version fixed this on my computer. @Predelnik Could you uninstall PyGitUp and then reinstall the dev version to make sure? |
Yeah, I noticed the |
I've filed an issue in colorama (which is responsible for converting ANSI codes to Win32 calls): tartley/colorama#49 |
(Just for info you need to add Yes I can confirm the the latest dev version fixes the colors, just as @Predelnik said the |
Is that still an issue with PyGitUp 1.4.0? |
Looks fixed for me: cmd.exe and MINGW32 are much improved and have switched the But Git Bash (MINGW64) has lost its colours. I've made a new issue for this different problem: #48. |
Okay, we'll track that on the issue you've opened. |
I'm getting the following output on Windows (both in Command Prompt, as well as in Git Bash). Looks like I'm missing something?
The text was updated successfully, but these errors were encountered: