With zsh as default shell, all commands think their name is "ghostty"

[elerch]

Steps to reproduce:

1. Set your shell to zsh
2. Run ghostty using this appimage
3. ps --help

This produces the following output:

Usage:
 ghostty [options]

 Try 'ghostty --help <simple|list|output|threads|misc|all>'
  or 'ghostty --help <s|l|o|t|m|a>'
 for additional help text.

For more details see ps(1).

It's not your fault! But it is, apparently, your problem. Digging into this, it appears as though it's caused by appimage setting the environment variable ARGV0, which zsh looks for to set argv[0] for commands. By running the following commands, you can see this behavior:

1. unset ARGV0
2. exec zsh
3. ps --help

At this point, ps is now aware it is "ps" and not "ghostty".

AppImage/AppImageKit#852

My guess is that adding unset ARGV0 here should do the trick: https://github.com/psadi/ghostty-appimage/blob/main/build.sh#L94

[elerch]

Anyone finding this through search, it is possible to workaround this issue by adding the following to .zshrc:

if [ -e "$ARGV0" ] && [ "$ARGV0" = "ghostty" ]; then
  unset ARGV0
  exec zsh
fi

[Samueru-sama]

oh shit I'm very sorry, I actually know about this issue since I had it with other appimages that I have.

The AppImage folks set ARGV0 in the AppImage runtime that points to the path to the AppImage without symlinks resolved, this is very useful if you ship several binaries in an AppImage since you can do your own busybox like implementation of having several bins in one like I do here.

The issue is that this conflicts with zsh's ARGV0, in the example I gave I actually transfer ARGV0 to a different BIN variable and then unset ARGV0, fixing.