Skip to content

fix: support Windows PowerShell 5.1 parsing - #5

Merged
user3301 merged 1 commit into
mainfrom
fix/windows-powershell-5-compatibility
Aug 1, 2026
Merged

fix: support Windows PowerShell 5.1 parsing#5
user3301 merged 1 commit into
mainfrom
fix/windows-powershell-5-compatibility

Conversation

@user3301

@user3301 user3301 commented Aug 1, 2026

Copy link
Copy Markdown
Owner

No description provided.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR improves Windows PowerShell 5.1 compatibility by removing Unicode em dashes from the setup script’s text/comments and by adding a Makefile check that validates parsing under Windows PowerShell 5.1.

Changes:

  • Replaced Unicode em dashes () with ASCII hyphens (-) in setup.ps1 user-facing output and comments.
  • Extended make check to additionally parse all .ps1 files using powershell.exe (Windows PowerShell 5.1), alongside the existing pwsh-based checks.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
setup.ps1 Replaces Unicode em dashes with ASCII hyphens to avoid PowerShell 5.1 parsing/encoding pitfalls.
Makefile Adds a Windows PowerShell 5.1 parse pass to make check to catch Desktop-edition parser incompatibilities.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@user3301
user3301 merged commit 53f3514 into main Aug 1, 2026
1 check passed
@user3301
user3301 deleted the fix/windows-powershell-5-compatibility branch August 1, 2026 23:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants