Having difficulties with the resurrection of the last closed workspace

[ChrisGVE]

I've set up my Western configuration with a listener on gui-startup as per the documentation. However, whenever I close and re-open Western, no restore takes place (I'm primarily using the default workspace at this point).

I'm using an iMac with everything up to date (latest beta 15.4) and all packages, including wezterm, managed by homebrew.

At the moment, I am working on a fork of resurrect.wezterm to add a new feature, but this should not affect the workspace resurrection at startup.

I've configured my wezterm listener, as follows:

-- resurrect the last closed workspace
wezterm.on("gui-startup", function()
	wezterm.log_info("gui-startup:", "resurrect starting")
	resurrect.state_manager.resurrect_on_gui_startup()
	wezterm.log_info("gui-startup:", "resurrect ended")
end)

But I don't even see a log_info in the debug window.

I suspect I am missing something very simple, but I can't seem to see it or make this work as intended.

Any help would be appreciated.

[MLFlexer]

Strange, my setup is just the line:

wezterm.on("gui-startup", resurrect.state_manager.resurrect_on_gui_startup)

which i have at the bottom of my config, just before the return config statement at the EOF.

Have you updated to the lastest version of the plugin?

another way to debug it is so open wezterm from another terminal, or within wezterm by using wezterm start --always-new-process and checking the output in the terminal.

[ChrisGVE]

Thanks, I’ll have a look. At the moment I am debugging my pull request also via the terminal output. Hopefully you get it sometimes today.

…

On 15 Mar 2025, at 2:12 PM, Malthe Larsen ***@***.***> wrote: Strange, my setup is just the line: wezterm.on("gui-startup", resurrect.state_manager.resurrect_on_gui_startup) which i have at the bottom of my config, just before the return config statement at the EOF. Have you updated to the lastest version of the plugin? another way to debug it is so open wezterm from another terminal, or within wezterm by using wezterm start --always-new-process and checking the output in the terminal. — Reply to this email directly, view it on GitHub <#104 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABULIJIVMP3S2WALDNPDPL2UQRLRAVCNFSM6AAAAABZBLHXT2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENJQHE3DOMQ>. You are receiving this because you authored the thread.