-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
4 changed files
with
56 additions
and
1 deletion.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2192,3 +2192,6 @@ DSN | |
PDO | ||
mysqli | ||
RDBMS | ||
Ghostty | ||
ghostty | ||
vNinja |
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
# Unsuitable Terminal | ||
|
||
*ghostty* is a new formidable terminal emulator. I wanted to try it out, but when I attempted to SSH to some remote hosts I got the following error: | ||
|
||
```text | ||
missing or unsuitable terminal: xterm-ghostty | ||
``` | ||
|
||
I did some _googling_ and found [a blog post][vninja], which suggested 3 different workarounds. | ||
|
||
One was updating `term_info` on the remote host, this is somewhat cumbersome and not something I wanted to maintain going forward with updates on the remote host. | ||
|
||
Second was by the blog post author and involved changing the `TERM` environment variable to something more recognisable than: `xterm-ghostty`. | ||
|
||
```shell | ||
[[ "$TERM_PROGRAM" == "ghostty" ]]; then | ||
export TERM=xterm-256color | ||
``` | ||
|
||
The last one, which I chose to go with was changing my SSH configuration on my local machine, so the environment variable was set as part of the SSH configuration: | ||
|
||
```text | ||
SetEnv TERM=xterm-256color | ||
``` | ||
|
||
The last part works like a charm as sort of does the same as the second one. | ||
|
||
## Resources and References | ||
|
||
- [vNinja.net: "Ghostty — Workaround for Missing or Unsuitable Terminal xterm-ghostty"][vninja] | ||
|
||
[vninja]: https://vninja.net/2024/12/28/ghostty-workaround-for-missing-or-unsuitable-terminal-xterm-ghostty/ |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
# Ghostty Visor | ||
|
||
*Ghostty* has a nifty feature of a terminal window you can access easily even if *Ghostty* is not the active application. | ||
|
||
I have mapped this to: `<shift>`-`<command>`-`<t>`. | ||
|
||
So if *Ghostty* is running, I have an easily accessible terminal (visor). The feature is called quick terminal, but I have seen it referred to as a visor from other applications and in the requests for the feature in *Ghostty*. | ||
|
||
- ["Request: Quake-style (Visor) Overlay Terminal Mode"](https://github.com/ghostty-org/ghostty/discussions/3733). | ||
|
||
## Resources and References | ||
|
||
- [Ghostty Documentation](https://ghostty.org/docs/config/keybind/reference#toggle_quick_terminal) |