With 1.1.2 I'm getting: "warning: Could not set up terminal for $TERM 'xterm-24bit'. Falling back to hardcoded xterm-256color values"

[pbgc]

Everything was working great with 1.0 (and works with Alacritty, Kitty, rio etc) and I have xterm-24bit defined and working

[taylrfnt]

Can you provide some more information on how you're setting this?

Ghostty's default TERM is xterm-ghostty.

If you can include if this is via SSH, on local, and your Ghostty configuration, that'd be a great start!

[pbgc]

@taylrfnt

It's local. I'm setting it with 'set -x TERM xterm-24bit' (fish) - I have this for ages and works without any problem with other terminals and worked with Ghostty 1.0

My Ghostty configuration:

command = "/opt/homebrew/bin/fish"
window-padding-x = 2
window-padding-y = 2
window-padding-balance = true
font-size = 13.0
font-family = "MesloLGS NF"
adjust-cell-height = -1
theme = "nightfox"
macos-option-as-alt = true
keybind = shift+alt+8=text:{
keybind = shift+alt+9=text:}
keybind = alt+8=text:[
keybind = alt+9=text:]
keybind = alt+3=text:€
keybind = alt+2=text:@
keybind = cmd+w=ignore
keybind = alt+right=unbind
keybind = alt+left=unbind

EDIT: added screenshot

[rhodes-b]

I dont think terminfo has changed at all between 1.0.0 and now, but you shouldnt be doing this anyways Ghostty is not xterm-24bit there are features it does not support in that terminfo file you made, while the terminfo ghostty ships with has features that one above does not support.

TL;DR it doesnt matter if it works in other terminals each terminal supports different features.

Maybe the behavior of how the fallback for xterm-256color works changed, which is the suggested fallback terminfo if you cant use xterm-ghostty

https://ghostty.org/docs/help/terminfo
please read the docs above if your issues is ssh add the env config option like that suggests what you are doing is kind of unsupported because you are trying to advertise ghostty as something it is not

grepping the ghostty repo this is the only mention of xterm-256color

ghostty/src/termio/Exec.zig

Line 760 in e07b6fd

try env.put("TERM", "xterm-256color");

Are you sure this is not something with fish? 4.0 recently came out which was a complete rewrite

a screenshot of where the error happens might be useful, since we dont know if it was the shell or ghostty saying that error it was not loading for me before

This is likely something to do with new fish version instead of new ghostty version

[pbgc]

@rhodes-b

Ghostty is not xterm-24bit ... but xterm-24bit is known and very used (I use it for a long time with MacOS and Linux and never had any problem).
It seems to me that the "problem" is that Ghostty does not know about it (but I'm 100% sure that with 1.0 I never got this message) and for example alacritty knows it. With alacritty (and kitty and rio etc) I can define TERM to alacritty or xterm-24bit and both work even if alacritty is the preferred one. If I define TERM as ghostty and run alacritty I get the exact same message: "warning: Could not set up terminal for $TERM 'ghostty'. Falling back to hardcoded xterm-256color values" (screenshot attached).

Thank you @taylrfnt @rhodes-b for the answers

[rhodes-b]

If you grep ghostty for "Could not setup" that does not show up in ghostty source? Does bash / zsh etc have that exact same error I think this is the shell printing this error not ghostty

[rhodes-b]

Definetly looks like Fish not Ghostty here
https://github.com/fish-shell/fish-shell/blob/cc455ff97677c0085de480f37af05d07d127739e/src/env_dispatch.rs#L563

maybe helps but I assume you arent on nix so im not sure
NixOS/nixpkgs#36146 (comment)

[pbgc]

@rhodes-b you are 100% right ... just tried! and yes .. I just updated do fish 4.0 ...
Sorry for the time and thanks a lot for the help!

[taylrfnt]

I was hoping it'd be an easy fix with a missing terminfo entry, but since it's present I am inclined to agree that this might be a side effect of the new fish shell release. The error here is from fish, not Ghostty, based on the information provided (if you have Ghostty logs that prove otherwise, please share them!).

I'm not a fish user (posix compliance is a must for me), so I may not be much help in troubleshooting the error on the fish side.

EDIT: looks like GitHub just didn't refresh while I typed. Glad this was solved.