-
Notifications
You must be signed in to change notification settings - Fork 678
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
Include scrollback history in state restoration #1847
Comments
I wrote some details on Terminal.app's behavior here in #2679 that it might be good to reference for anyone doing this. |
Nice writeup. This feature is one I have come to rely on, especially the per window command history. I wonder if implementing the "TERM_SESSION_ID env var containing a UUID that's unique per window/tab and persists across relaunch" part would enable the shell to handle most of this without any additional work on the ghostty side? At the least this TERM_SESSION_ID idea is one that seems to provide the bare necessity for me the user, if I wanted to try and "hack" around this missing feature by restoring sessions to particular windows/splits with eg. zellij. To be clear, TERM_SESSION_ID would need to be unique for each split. It might be helpful to have unique ID's for tabs and windows, in addition. Also, I don't think this issue being labeled os/macos is correct, this is a feature to match functionality on the mac os Terminal.app, but this is a cross platform feature, I know I would love it on linux also. |
FWIW, this is the single missing feature that is blocking me from jumping fully to ghostty as my daily driver. Everything else, i depend on, works reliably and pretty damn fast. |
Oh, the pain. I was lured into pressing "Update and restart" just a minute ago and to my surprise ALL context of what I had been working on was gone and forgotten. My mistake obviously, but I was under the impression that "Same working directory" & "Restore text when reopening" was a an early implemented core feature already. Let's make it a configurable option defaulting to True 😉 |
This is especially useful for updates and crashes, but it's nice to preserve history in general.
(I haven't attempted this one)
The text was updated successfully, but these errors were encountered: