PowerShell on osx - how to force to be completely monochrome

Open
#3,918 19 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, powershell
Domain
cli

Research direction

Start by reproducing the unreadable typed text in a macOS terminal of type "Man Page" using pwsh, then inspect PSReadLine's color handling and terminal capability detection. Done means typed text remains visible on terminals with white or yellow backgrounds, ideally respecting the TERM environment variable.

Written by the indexing model from the issue text.

Description

Needs-Triage :mag:
Prerequisites
  • Write a descriptive title.
  • Make sure you are able to repro it on the latest released version
  • Search the existing issues, especially the pinned issues.
Exception report

See PowerShell on osx how to force to be completely monochrome

Should be able to easily use PowerShell on a monochrome terminal, ideally respecting the TERM environment variable.
Screenshot

Image 14-01-24 at 08 39

Environment data
Name                           Value
----                           -----
PSVersion                      7.4.1
PSEdition                      Core
GitCommitId                    7.4.1
OS                             Darwin 23.2.0 Darwin Kernel Version 23.2.0: Wed Nov 15 21:53:34 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T8103
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0
Steps to reproduce

Open a terminal on macOS of type "Man Page", use pwsh

Typed text will be yellow on a yellow background

Expected behavior

Typed text should be visible no matter the type of terminal or colours used by the terminal

Actual behavior

Typed text is always yellow, hard to read on white or yellow backgrounds.

Dominant language
C#
Stars
4.4k
Forks
341
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PowerShell/PSReadLine

All issues in PowerShell/PSReadLine

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.