-e flag for ghostty +new-window does not work

[ndreas]

Issue Description

Following https://ghostty.org/docs/linux/systemd and enabling the user systemd service, ghostty +new-window spawns a new window via the service as expected, but supplying a command using ghostty +new-window -e /usr/bin/top does not work, which ghostty +new-window --help says should work.

I have tested this on a fresh Arch install inside Sway, as well as NixOS running Hyprland.

Expected Behavior

ghostty +new-window -e /usr/bin/top should start a new window running top

Actual Behavior

ghostty +new-window -e /usr/bin/top runs the default shell

Reproduction Steps

1. Configure the systemd service according to https://ghostty.org/docs/linux/systemd
2. Run ghostty +new-window -e /usr/bin/top

Ghostty Logs

No response

Ghostty Version

Ghostty 1.2.0

Version
  - version: 1.2.0
  - channel: stable
Build Config
  - Zig version   : 0.14.1
  - build mode    : builtin.OptimizeMode.ReleaseFast
  - app runtime   : apprt.Runtime.gtk
  - font engine   : font.main.Backend.fontconfig_freetype
  - renderer      : renderer.generic.Renderer(renderer.OpenGL)
  - libxev        : io_uring
  - kernel version: 6.12.48
  - desktop env   : other
  - GTK version   :
    build         : 4.18.6
    runtime       : 4.18.6
  - libadwaita    : enabled
    build         : 1.7.6
    runtime       : 1.7.6
  - libX11        : enabled
  - libwayland    : enabled

OS Version Information

NixOS unstable, Arch Linux

(Linux only) Display Server

Wayland

(Linux only) Desktop Environment/Window Manager

Hyprland, Sway

Minimal Ghostty Configuration

quit-after-last-window-closed = false

Additional Relevant Configuration

No response

I acknowledge that:

• I have reviewed the FAQ and confirm that my issue is NOT among them.
• I have searched the Ghostty repository (both open and closed Discussions and Issues) and confirm this is not a duplicate of an existing issue or discussion.
• I have checked the "Preview" tab on all text fields to ensure that everything looks right, and have wrapped all configuration and code in code blocks with a group of three backticks (```) on separate lines.

[mitchellh]

The docs should be updated, we didn't get this in for 1.2.0 and don't consider this a bug. This will ship in a 1.3. I'll make an issue to track it though.

[mitchellh]

#8862