[MacOS] window-inherit-working-directory enabled but unexpectedly not working #4176
Replies: 6 comments 3 replies
-
Oh good, I thought I must be the only one with this issue! I've been using Ghostty since release day and have always experienced this issue. |
Beta Was this translation helpful? Give feedback.
-
I'm not 100% sure, but it seems that in my case the problem was fixed when updating my oh-my-zsh setup ( |
Beta Was this translation helpful? Give feedback.
-
@WizardOfMenlo and @johnallen3d are either of you using I'm digging into it a bit more and will follow up. |
Beta Was this translation helpful? Give feedback.
-
@aryounce Hey, no I am using |
Beta Was this translation helpful? Give feedback.
-
I have found that cmd+D or cmd+T fails to open current directory if I've got a running Vitest dev process going (might be the same for other running processes? 🤷♂️). This is pretty much the only bug I've experienced in Ghostty so kudos to that! 😄 |
Beta Was this translation helpful? Give feedback.
-
For me when pwd contains a I use Ghostty 1.0.1, macOS 15.2, zsh 5.9 |
Beta Was this translation helpful? Give feedback.
-
Hi, I have been using Ghostty for a week now and it has worked like a charm.
Today, the window-inherit-working-directory feature has unexpectedly stopped working.
Expected behaviour: I cd into a directory, press Cmd+D to open a tab, and that tab is in the same directory
Observed behaviour: the tab opens in the ~ directory instead.
Config
Version:
Beta Was this translation helpful? Give feedback.
All reactions