-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is it possible that this could cause Ghostty to hang on long running processes? #148
Comments
That repository doesn't seem to be available. Maybe it is private? |
Ah yes it is, I apologize. https://mitchellh.com/ghostty @mitchellh might be able to add you if you want. It's his awesome NEW terminal. With |
Hello! I'd be happy to add you @franciscolourenco but I consider any functionality that works in other terminals and not mine a bug with my own terminal 😄 So I don't think this is a |
Thank you @mitchellh, that makes sense :) |
Sorry @franciscolourenco you can't see our issue but I've tracked this down to an upstream issue: julienXX/terminal-notifier#301 Specifically from my thread:
I'm not sure why it hangs with the Ghostty ID. But it appears based on the previous issue this isn't unique. I don't see any smoking guns in logs anywhere. |
Btw, I was surprised to see that Their usage: OSC 9
OSC 777
|
@mitchellh unfortunately this doesn't work when the process is in a detached tmux session or the shell is otherwise not interactive |
True! But if the shell is interactive and it's not tmux, it does work, which I feel would still be pretty common? |
ping |
I'd say if you were thinking about implementing @mitchellh ideas we could keep this open @franciscolourenco otherwise I think we can close it. |
@blacktop will have to follow up on OSC 9 and OSC 777 in a different thread. I'll leave this open for now just for reference. Thanks! |
Please see https://github.com/ghostty-org/ghostty/issues/1917
The text was updated successfully, but these errors were encountered: