Skip to content

Overriding $TERM to a more compatible value like xterm-256color #828

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 29, 2025
Merged

Overriding $TERM to a more compatible value like xterm-256color #828

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
45397b9
docs(troubleshooting): overriding the $TERM to a more compatible valu…
danterolle Sep 11, 2025
00d0ecc
docs(troubleshooting): update terminal type workaround to use env
danterolle Sep 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/Developer-Guide_Build-Preparation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,6 +68,16 @@ Run framework:
./compile.sh [command] [switch...] [config...]
```

!!! tip "Troubleshooting: 'unknown terminal type' error"
When running the script, especially from modern terminal emulators (like Ghostty, Kitty, WezTerm), you might encounter an error like

'xterm-ghostty': unknown terminal type

**Quick workaround:** you can force a more common terminal type before running the script:
```bash
env TERM=xterm-256color ./compile.sh
```

Only one command can be specified.

Switches are parameter settings that are used by the build framework itself
Expand Down