-
Notifications
You must be signed in to change notification settings - Fork 3k
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
terminal colour settings #17325
Comments
Hi, I can't find out how to either reset or change the Azure CLI Cloud Shell terminal settings. I have larger scripts now and find the black background I changed it to difficult to use. Thanks. |
color |
Tried it.
Can you give me more?
Alan
… Il giorno 16 mar 2021, alle ore 12:48, yonzhan ***@***.***> ha scritto:
color
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
az config set core.no_color=true # no change az config --help # nothing Microsoft Docs for "color" in AZ CLI # nothing |
@Skmonkay, I see what you are talking about. Azure CLI This screenshot you shared is coming from My repoI can see the same result while running PowerShell terminal doesn't look better for Solution 1: Change font to MonospaceYou may change the font to Monospace which is bolder than Courier New. Solution 2: Use VS Code editorThe VS Code editor (GUI) are available for both Bash and PowerShell: Note that the file extension |
The colors in Cloud Shell (including the background) are not configurable, and that's why Azure CLI hardcodes RGB colors to get better visual effect in Cloud Shell (#17283). I have also created Azure/CloudShell#84 to track this readability issue. |
Hi, Yeah, I came to the same conclusions as you. I'll have to live with it and stick with the VS Code Editor. Thanks. Alan |
@Skmonkay, I am glad to know the workaround works for you. You may also vote on these issues: |
Resource Provider
Description of Feature or Work Requested
Minimum API Version Required
Swagger Link
Target Date
The text was updated successfully, but these errors were encountered: