fix(ps1): strip all non-ASCII Unicode from PowerShell scripts
Windows PowerShell 5.1 reads .ps1 files without BOM as Windows-1251 by default. Em-dashes (-) and other Unicode chars in string literals get mangled into invalid bytes (e.g. "session - no" becomes garbage that breaks the parser with "Unexpected token" errors. Replaced em-dash, en-dash, smart quotes, ellipsis, NBSP and arrows with their ASCII equivalents across all 12 .ps1 scripts (install/update/ uninstall for claude/gemini/codex/qwen). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
# Claude Code — Windows Updater
|
||||
# Claude Code - Windows Updater
|
||||
# Usage: powershell -ExecutionPolicy Bypass -File claude\uclaude_update.ps1
|
||||
#
|
||||
# Updates Claude Code via npm registry + re-applies config patches.
|
||||
|
||||
Reference in New Issue
Block a user