Regression in 1.3.0: Multi-line Bash PS1

[dblume]

Issue Description

This is a regression in Ghostty 1.3.0 (Or 1.3.0 exposing a bug in my shell script.)

I use Bash, and my .bashrc includes a multi-line PS1 that worked with the previous Ghostty before 1.3.0.

export PS1='$(if [ $? -eq 0 ]; then echo -e "P";
              else echo -e "F";
              fi) $ '

(The real one is longer, and justifies being multiple lines, this is a simple example.)

Workaround

If I put the PS1 on one line, it'll work.

export PS1='$(if [ $? -eq 0 ]; then echo -e "P"; else echo -e "F"; fi) $ '

Expected Behavior

P $

Actual Behavior

bash: command substitution: line 3: syntax error near unexpected token `)'
bash: command substitution: line 3: `
              fi) $ '
bash: command substitution: line 3: syntax error near unexpected token `)'
bash: command substitution: line 3: `
              fi) $ '

Reproduction Steps

1. Use Bash for your shell on a Mac device.
2. Open Ghostty
3. Observe Bash prompt.

Ghostty Logs

Filtering the log data using "subsystem == "com.mitchellh.ghostty""
Timestamp                       Thread     Type        Activity             PID    TTL
2026-03-09 10:00:36.642487-0700 0x169c5    Info        0xbb99e              6401   0    ghostty: [com.mitchellh.ghostty:ghostty] known but unimplemented action action=40
2026-03-09 10:00:36.647272-0700 0x169c5    Info        0xbb99e              6401   0    ghostty: [com.mitchellh.ghostty:io_exec] io_exec: found Ghostty resources dir: /Applications/Ghostty.app/Contents/Resources/ghostty
2026-03-09 10:00:36.647451-0700 0x169c5    Info        0xbb99e              6401   0    ghostty: [com.mitchellh.ghostty:io_exec] io_exec: shell integration automatically injected shell=.bash
2026-03-09 10:00:36.647615-0700 0x169c5    Info        0xbb99e              6401   0    ghostty: [com.mitchellh.ghostty:ghostty] known but unimplemented action action=22
2026-03-09 10:00:36.652276-0700 0x203f7    Info        0x0                  6401   0    ghostty: [com.mitchellh.ghostty:io_exec] io_exec: started subcommand path=/usr/bin/login pid=12616

Ghostty Version

Ghostty 1.3.0

Version
  - version: 1.3.0
  - channel: stable
Build Config
  - Zig version   : 0.15.2
  - build mode    : .ReleaseFast
  - app runtime   : .none
  - font engine   : .coretext
  - renderer      : renderer.generic.Renderer(renderer.Metal)
  - libxev        : kqueue

OS Version Information

Sequoia 15.7.3

(Linux only) Display Server

None

(Linux only) Desktop Environment/Window Manager

No response

Minimal Ghostty Configuration

# Everything commented out, still reproducible.

Additional Relevant Configuration

Just so you know which bash I run, it's Homebrew's 5.3.9.

$ ps -p $$
  PID TTY           TIME CMD
40841 ttys000    0:00.50 -/usr/local/bin/bash --posix
$ ls -l /usr/local/bin/bash
lrwxr-xr-x@ 1 root  wheel  22 Dec 15 12:18 /usr/local/bin/bash -> /opt/homebrew/bin/bash
$ ls -l /opt/homebrew/bin/bash
lrwxr-xr-x@ 1 dblume  admin  29 Dec 15 08:25 /opt/homebrew/bin/bash -> ../Cellar/bash/5.3.9/bin/bash

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]

cc @jparise

[jparise]

I haven't been able to reproduce this yet using the same bash version and PS1 recipe. I'll keep looking.

[dblume]

There may be interaction with another file like my .inputrc? Here are all my dotfiles. I'm happy to try to help isolate when I can.

[dfsnow]

I'm seeing something similar and possibly related. I have a vim mode indicator in my .inputrc that worked fine in 1.2.3, but now breaks to a second line in 1.3.0.

Setting these lines in .inputrc, toggling modes with I and escape, then typing a command is enough to cause the behavior:

set vi-cmd-mode-string "\1\e[48;5;4m\2\1\e[1;38;5;18m\2 N \1\e[0m\2 \1\e[0 q\2"
set vi-ins-mode-string "\1\e[48;5;2m\2\1\e[1;38;5;18m\2 I \1\e[0m\2 \1\e[6 q\2"

1.3.0 looks like:

1.2.3 looked like:

[dfsnow]

@dblume I can indeed reproduce the original issue. A minimal bashrc with just your PS1 produces the same error for me. I'm not sure the two issues are actually related though, as the PS1 errors happen regardless of whether I have vim mode on in bash.

[dblume]

Aside, @dfsnow , you taught me about the vi mode strings here, and I love changing the cursor with the mode, just like in nvim. Thank you for that!

set vi-cmd-mode-string "\1\e[2 q\2"
set vi-ins-mode-string "\1\e[6 q\2"

Back on topic: These directives work fine in Ghostty 1.3.0. So the extra linebreaks come from the other parts of the strings.

[jparise]

I think the vi mode-specific issues here are a separate issue. I'm looking at them, too. It's similar to #10953.

[jparise]

#11377 should fix the extra newlines appearing when show-mode-in-prompt is enabled.

[dfsnow]

That does it! Thanks for the quick fix @jparise

[ahatzz11]

I believe I'm seeing something related. After the first command, my line prompt becomes multiple lines.

[jparise]

#11369 should fix the root issue: we were inserting secondary prompt markers for literal newlines (in addition to prompt newline sequences).

That's why putting it all on one PS1=... line worked while the multi-line format did not.

[ahatzz11]

@jparise Are we sure this is fixed? I am still seeing some issues with my prompt being defined across multiple lines and forced newlines being in my prompt, version ab269e2c7

Original prompt (zsh):

PROMPT='$FG[237]------------------------------------------------------------%{$reset_color%}
$FG[032]%~\
$(git_prompt_info) $(kube_context_prompt_info) \
$FG[105]%(!.#.») %{$reset_color%}'

output in ghostty:

------------------------------------------------------------
~/code/frontend
(branch:fix-email-validation) ⎈ test
»

If I change my prompt to a single line, then its fine.

single line prompt:

PROMPT='$FG[237]------------------------------------------------------------%{$reset_color%}
$FG[032]%~$(git_prompt_info) $(kube_context_prompt_info) $FG[105]%(!.#.») %{$reset_color%}'

output in ghostty:

------------------------------------------------------------
~/code/frontend(branch:fix-email-validation) ⎈ test »

[jparise]

@ahatzz11 this issue is about bash, but it looks like you're using zsh?

[dblume]

Confirmed the fix for the original Bash PS1 issue with the nightly build built at 7068573. Thank you!

[ahatzz11]

@jparise ah you're right - I've been using zsh and not bash, I conflated those two things. Sorry about that! That said - I just put back my multi-line declaration of my prompt and it seems like it's been patched for ZSH as well. Thanks!