PSReadline unusable on ServerCore container - #3937
Merged
Jason Shirk (lzybkr) merged 1 commit intoJun 5, 2017
Merged
Conversation
…on ServerCore but fails running in container to allow PSReadline to continue
Jason Shirk (lzybkr)
approved these changes
Jun 5, 2017
Thatgfsj (Thatgfsj)
pushed a commit
to Thatgfsj/PowerShell
that referenced
this pull request
Aug 6, 2026
…l#3937) The api is available on ServerCore but fails (returns false) running in container. Silently ignoring the failure allows PSReadline to work.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The GetCurrentConsoleFontEx() api is available, but fails with unspecified error code on ServerCore running in container. Using similar logic to NanoServer where the api is not available, don't make the error fatal. Ignore the error so PSReadline continues to work. Impact is if using ServerCore on non-English (double char wide) characters.
Fix #3927