-
Notifications
You must be signed in to change notification settings - Fork 118
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
starting a shell contains old commands/output #851
Comments
That's indeed a request by Apple's user experience rules: the app should restart as it was when the user left it. So when a-Shell moves to the background, it saves its current state (directory, environment variables, output...) and restores it when it is reopened. |
Thank you for the speedy answer, I turned the app of, but the python venv is still active when I start the app. Also I am not in the $HOME directory. |
That shouldn't happen, but I'm going to check the code to make sure. You also need to make sure the app has been terminated, instead of just sent to the background (double click on the home button to make the app switcher appear, then slide upward to terminate the app). |
I'm positive, that I always terminated the app. It wasn't just in the background. Cheers! |
Hi,
when I start the app. It is stuck in the directory I was last in, with the venv I last sourced and has all sort of outputs from previous commands. The outputs are not the most recent ones.
I tried adding a
.profile
/.bashrc
but it doesnt have any effect. Neither does the neWindow command.Is this the intended behaviour. I would like the app to start with a fresh shell every time I use it.
Thanks for you help!
PS: I am on an iPhone 16pro - IOS 18.1.1
The text was updated successfully, but these errors were encountered: