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
{{ message }}
This repository has been archived by the owner on Mar 20, 2023. It is now read-only.
On macOS, the default terminal is black text on a white background (and since I have difficulty seeing red-on-black, I prefer to keep it that way). As a result, when cargo-expand uses prettyprint, certain syntax elements become invisible white-on-white text that renders the output unusable.
Options
Somehow detect the terminal background color and choose a contrasting color for primary text. Doing this in a cross-platform way might be difficult.
Add an option for callers to tell prettyprint to use a light theme vs a dark theme. This would require cargo-expand and others to expose a command-line flag of their own to choose light vs dark, but it would avoid reading anything from the terminal.
The text was updated successfully, but these errors were encountered:
This can be done already. Prettyprint supports all colorschemes that syntect supports. So it might be as easy as sending a pull request to cargo-expand (or cargo-inspect, which is also using prettyprint) and add the flag as well as choose a colorscheme.
This is now done in cargo-inspect thanks to @jonathansty.
See the release notes here.
It uses prettyprint 0.4.0, which has support for the get_themes method. See here.
On macOS, the default terminal is black text on a white background (and since I have difficulty seeing red-on-black, I prefer to keep it that way). As a result, when
cargo-expand
usesprettyprint
, certain syntax elements become invisible white-on-white text that renders the output unusable.Options
prettyprint
to use a light theme vs a dark theme. This would requirecargo-expand
and others to expose a command-line flag of their own to choose light vs dark, but it would avoid reading anything from the terminal.The text was updated successfully, but these errors were encountered: