Timmy_Foundation/hermes-agent
15
0
Fork 0
Code Issues 253 Pull Requests 24 Actions 10 Packages Projects Releases Wiki Activity

docs: fix salvaged PR #980 troubleshooting details

Browse Source 
Correct the PowerShell UTF-8 snippet in the new Windows encoding tip
and soften the Docker CLI wording to match Hermes' actual lookup
behavior.
This commit is contained in:
teknium1
2026-03-14 06:02:57 -07:00
parent 767b5463f9
commit dd6a5732e7
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
website/docs/guides/tips.md
View File

@@ -192,13 +192,13 @@ with open("results.txt", "w", encoding="utf-8") as f:
f.write("✓ All good\n")
```
- In PowerShell, you can also set UTF-8 as the default output encoding for your session:
- In PowerShell, you can also switch the current session to UTF-8 for console and native command output:
```powershell
$PSStyle.OutputEncoding = [Console]::OutputEncoding = [Text.UTF8Encoding]::new($false)
$OutputEncoding = [Console]::OutputEncoding = [Text.UTF8Encoding]::new($false)
```
This matches how the CI environment behaves and helps avoid Windows-only failures.
This keeps PowerShell and child processes on UTF-8 and helps avoid Windows-only failures.
### Review Before Choosing "Always"