search

holzschu / a-shell

A terminal for iOS, with multiple windows
BSD 3-Clause "New" or "Revised" License
2.75k stars 117 forks source link

starting a shell contains old commands/output #851

Open ChristianF88 opened 1 week ago

ChristianF88 commented 1 week ago

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

holzschu commented 1 week ago

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. You can deactivate this behaviour using the "Settings" app: deactivate "Keep screen content between sessions".

ChristianF88 commented 1 week ago

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.

holzschu commented 1 week ago

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).

ChristianF88 commented 1 week ago

I'm positive, that I always terminated the app. It wasn't just in the background. Cheers!