You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently terminal color codes are read once during daemon start-up, and then re-used on each run. So if the daemon is started in one environment (e.g. an IDE plugin) where colors are not available, and then run in another where they are available (e.g. a normal terminal), the colors stay disabled until the next daemon restart.
This is probably low priority because people don't often switch between running mypy daemon in a terminal and in IDE, and this doesn't cause mangled formatting.
The text was updated successfully, but these errors were encountered:
Currently terminal color codes are read once during daemon start-up, and then re-used on each run. So if the daemon is started in one environment (e.g. an IDE plugin) where colors are not available, and then run in another where they are available (e.g. a normal terminal), the colors stay disabled until the next daemon restart.
This is probably low priority because people don't often switch between running mypy daemon in a terminal and in IDE, and this doesn't cause mangled formatting.
The text was updated successfully, but these errors were encountered: