Why does iTerm beta implement a custom xterm-256color terminfo file?
Bug report
Hello!
I've identified the custom xterm-256color
terminfo file included with iTerm 3.5.0betaXX
as a necessary condition for an issue discovered in ttyplot. This is likely an issue with ttyplot, and not iTerm, but since it only occurs when using the terminfo file included in iTerm beta (~/Applications/iTerm.app/Contents/Resources/terminfo/78/xterm-256color
) I felt it would be worth raising an issue here too. See the issue created for ttyplot for details.
You can see that iTerm is using a custom terminfo file by running infocmp xterm-256color
. This custom terminfo is loaded because iTerm sets the TERMINFO_DIRS
environment variable, which you can see by running env | grep terminfo
, which prints the following for me:
TERMINFO_DIRS=/Users/q/Applications/iTerm.app/Contents/Resources/terminfo:/usr/share/terminfo
The stable version of iTerm uses the default macOS terminfo file at /usr/share/terminfo/78/xterm-256color
.
Can anyone explain why iTerm beta uses a custom terminfo file?
This may not be a bug in iTerm, but in case it's useful:
- iTerm2 version: 3.5.0beta19
- OS version: macOS 14
- Attach
~/Library/Preferences/com.googlecode.iterm2.plist
here: com.googlecode.iterm2.plist - Attach a debug log, if possible. N/A
- Attach a screen capture video if it would make the reproduction steps clearer. See the ttyplot issue
Detailed steps to reproduce the problem
See steps in the ttyplot bug report.