Skip to content

Conversation

@mickaelistria
Copy link
Contributor

@mickaelistria mickaelistria commented Oct 14, 2025

Fixes #3398

This command can be tried the following way:

Base

  1. Start an IDE with this patch
  2. Close some views
  3. Kill the IDE (brutally, not with the nice "exit" button)
  4. Restart: ❌ Closed views are here again

Diff

  1. Start an IDE with this patch
  2. Close some views
  3. Ctrl+3 > "Persist workbench state"
  4. Kill the IDE (brutally, not with the nice "exit" button)
  5. Restart: ✔️ Closed views are not there

@github-actions
Copy link
Contributor

github-actions bot commented Oct 14, 2025

Test Results

 3 018 files  ±0   3 018 suites  ±0   2h 21m 53s ⏱️ + 5m 4s
 8 226 tests ±0   7 977 ✅ ±0  249 💤 ±0  0 ❌ ±0 
23 598 runs  ±0  22 804 ✅ ±0  794 💤 ±0  0 ❌ ±0 

Results for commit ed34d7e. ± Comparison against base commit cbf687d.

♻️ This comment has been updated with latest results.

@mickaelistria mickaelistria force-pushed the persistWorkbenchCommand branch from a62e673 to ed34d7e Compare October 14, 2025 20:53
@mickaelistria mickaelistria force-pushed the persistWorkbenchCommand branch from 28fb204 to b7669ec Compare October 15, 2025 13:01
@mickaelistria mickaelistria merged commit 90de1f0 into eclipse-platform:master Oct 15, 2025
2 checks passed
@BeckerWdf
Copy link
Member

I think this is a nice an pragmatic addition

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

A command to store/persist current workbench state

2 participants