color output does not work for me #163
Replies: 5 comments 5 replies
-
and
|
Beta Was this translation helpful? Give feedback.
-
For clarification: I recently added the rich library to Trade-Dangerous, and made it accessible to TD code without rigorously imposing it on everything (*1). Doing that gives you various things immediately for free, including some basic syntax highlighting in output. It's also the library many other Python tools rely on for progress bars and spinners etc. TD already had some ancient color features ("--color") that I never got round to fleshing out, and I wouldn't expect anyone else to want to either(*2), especially when you have so many different contexts to support(*3). Much better to delegate that responsibility/overhead to rich. -- (*1 all TD code is supposed to write output via 'tdenv', but not all of it does, and only the code that does is currently taking advantage of rich. the idea is to eliminate the maintenance head of lots of custom terminaly-stuff currently coded into TD. Amongst other things, rich performs platform-compatibility and doing things like not writing color codes to files or between processes) |
Beta Was this translation helpful? Give feedback.
-
@nepomuk16321 Could you post a screenshot showing what you mean? Where you are expecting color that you aren't seeing it, the command line you are using? |
Beta Was this translation helpful? Give feedback.
-
The You don't see color output on your |
Beta Was this translation helpful? Give feedback.
-
The color output does not work for me, neither in the CMD window nor in the PowerShell window.
In the PS window, only the command line is displayed in color.
Beta Was this translation helpful? Give feedback.
All reactions