Skip to content
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

When updating, Warp should remember the tabs I had open #43

Closed
jubby2000 opened this issue Jul 21, 2021 · 6 comments
Closed

When updating, Warp should remember the tabs I had open #43

jubby2000 opened this issue Jul 21, 2021 · 6 comments
Labels
Feature requests Feature Requests

Comments

@jubby2000
Copy link

Is your feature request related to a problem? Please describe.
Not exactly.

Describe the solution you'd like
It would be nice if the path for each open tab (and the positions of each tab) were preserved on an update or when closing Warp altogether.

Additional context
What currently happens: All your tabs are closed and if you were working in multiple different paths, you have to open them all up again

@dimaqq
Copy link

dimaqq commented Oct 7, 2021

Better yet, warp should also keep terminal sessions alive and running processes alive.
iTerm2 does that.

my 2c: now, in early dev, when there are many releases, it's more important than later.

@ianribas
Copy link

The normal terminal on Mac OS also remembers the content of the tab (output of previous commands, maybe command search history?). Maybe opt in, but I think remembering everything would be great.

@elviskahoro elviskahoro changed the title When updating, Warp should remember the tabs I had open Sessions: When updating, Warp should remember the tabs I had open Nov 7, 2021
@elviskahoro elviskahoro changed the title Sessions: When updating, Warp should remember the tabs I had open Sessions: Restoration - When updating, Warp should remember the tabs I had open Nov 12, 2021
@zeh
Copy link

zeh commented Nov 19, 2021

Judging by similar, lengthly discussions in the Windows Terminal repo (#766, #961, others), this is a harder problem than it looks, and it means different things for different people.

There's several different expected features for full restoration support, from top to bottom:

  • Restore windows position
  • For each window, restore opened tabs
  • For each tab, restore opened folder
  • For each tab, restore scroll buffer
  • For each tab, restore (individual) command history
  • For each tab, restore running processes

So for Warp I can see a gradual approach being needed, where it does thing at a time. IMO each would already improve the user experience dramatically for those who like to live with a... complex terminal state. So I suppose my point is that a gradual approach towards this goal is fine!

For example, for Windows Terminal itself, they're still only at the third bullet point ("restore opened folders"), but not super functional, only on the "Preview" version, and it does require some prompt fiddling to get it working.

@fishcharlie
Copy link

Don't want to add too much noise. But coming from the native macOS Terminal, this is a major lacking feature in Warp. Force quitting the Terminal in macOS restores the contents of the terminal, commands & output. Looks like the default of this is 10k lines.

Hopefully Warp can prioritize this soon.

@elviskahoro elviskahoro changed the title Sessions: Restoration - When updating, Warp should remember the tabs I had open When updating, Warp should remember the tabs I had open Dec 6, 2021
@elviskahoro
Copy link

from #243 @ShukantPal

I updated Warp and the terminal was reset. It would be nice if

  1. The old processes were killed. I had to run killall mongod to restart my MongoDB instance.

OR

  1. The old processes aren't orphaned and the logs get preserved.

@elviskahoro
Copy link

Was added!

@warpdotdev-devx warpdotdev-devx bot added the Feature requests Feature Requests label Jan 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature requests Feature Requests
Projects
None yet
Development

No branches or pull requests

6 participants