+1 please add this fast ;D

@ivands Still have a few glitch! But working on it!

Commit e1ee608 close #1046

@matheuss @rauchg Review Needed

Any news?

We're going to be revisiting this PR very soon!

Yeah indeed. Engineering studies took a toll on me haven't had much time lately to dedicate any time on anything except studies. Life happens you know. Much love. ❤️

Session ended. Can start coding again!

Thread started on spectrum. thread

Any news since the last comment @ppot ?

@VinceBT I started a thread for this feature, but nobody answered yet!

@rauchg Any take on how you would see session restoration?

@chabou, @rauchg While trying to make a session restoration plugin. I came across this problem. Since I can't share a state between

exports.onApp = () => {
}

exports.onWindow = (window) => {
}

and

exports.middleware = (store) => (next) => (action) => {
}

I can't have a global state residing inside my plugin. The reason is since we decouple the backend and the front-end.

While I can listed to onWindow event for new window, I can store them great. Same for the middleware I can invoke specific action and create new recorded session with their desired state. But still. If I make a recorder on top of it. each window will have a undefined instance of the window it's create and if I make the recorder inside let say:

  if ('INIT' === action.type) {
      const window = new Window('INIT');
      record.onWindow(window);
      console.log(reccord);
  }

Each window will have one instance of the recorder. So how would we share this state between the two.

The ideal way would be to listed to the RPC localy inside the plugin on the hyper process level. The other way around would be to totally integrate the session recorder inside hyper-core like at the present level of this PR.

In order to have this possibility we could separate the RPC in two.

• One rendererRPC = which is the rendered Window.
  • decorating the Term
• One terminalRPC = which is the terminal process.
  • new window
  • new session
  • And so on..

One hacky way, which is code-smelling would be to have a stored state in a local file and make read/write action for every updated state which is not the goal here. No need to make multiple IO and slowing the term.

I am open for comment and suggestions.

Have the same feature request

One hacky way, which is code-smelling would be to have a stored state in a local file and make read/write action for every updated state which is not the goal here. No need to make multiple IO and slowing the term.

Reading this issue gave me flashbacks: I implemented session save/restore in Firefox 2 in 2006. It basically worked the way you describe here.

12 years later, Mozilla is almost finished making that code not slow (😂+😭), but protecting user data is a trade-off I'd make 100x over again.

Off-by-default-until-fast is a nice balance between performance and protection, if that's easier to swallow than some interim perf hit. But no protection option leaves us developers living in fear 😅

If not to restore sessions, is it currently possible to create some predefined (config layout) on the app start, so it would open needed tabs and split pane and need?

If not to restore sessions, is it currently possible to create some predefined (config layout) on the app start, so it would open needed tabs and split pane and need?

I use hypercwd and set initialWorkingDirectory to my desire

@caina-jumia I too use it, but I need tabs and split panes setup.

@ppot worth keeping this open or will you make a new one when you work on this again anyway?

@Stanzilla worth keep it open. I'm exploring the rust binding for speed

Oops miss clicked, alright then!

Is this dead?

Hey, @ppot! Have you any progress in this task?
It's really rescue thing, anyway.

Appositely, thank you a lot for you work!

This seems almost done, right ?

This seems almost done, right ?

No
It'll need to be updated as the codebase has been ported to typescript, and has changed quite a bit.

Hi reviewers, any status on this feature ?
Would be quite handy to have.

Hi Guys, I just want to understand the request as I'm working on something myself.

Is the request to save & restore tabs, panes, windows, positions and cwd for each?

Have I missed anything?

Hi reviewers, any status on this feature ?
Would be quite handy to have.

no updates right now, though it might be doable now as we've started releasing again and so the development should pick up a bit.

Hi Guys, I just want to understand the request as I'm working on something myself.

Is the request to save & restore tabs, panes, windows, positions and cwd for each?

Have I missed anything?

that's all I guess, you can also include restoring terminal content using xterm serialization addon if you want.

Hi reviewers, any status on this feature ?
Would be quite handy to have.

no updates right now, though it might be doable now as we've started releasing again and so the development should pick up a bit.

Hi Guys, I just want to understand the request as I'm working on something myself.
Is the request to save & restore tabs, panes, windows, positions and cwd for each?
Have I missed anything?

that's all I guess, you can also include restoring terminal content using xterm serialization addon if you want.

... From what I can see so far the serialization addon saves out the terminal buffer, not yet sure how that would be useful for restoring it because ultimately I assume the goal would be to restore the shell session which is a different issue especially the command state and process state in the shell.

I've already handled capture and save options of terminal content anyway and gone a little further than the serialisation addon.

Any ideas on approaching restoring the shell process state are very welcome