Skip to content

Conversation

@Thom1729
Copy link
Member

@Thom1729 Thom1729 commented Feb 23, 2021

Fix #147.

Includes #148 so the window_util tests will run.

One case is not tested. If you have an unsaved view in one window and a clone of that view in the second window, and you close_window() the second window, the first view should not be scratch afterward. However, it doesn't look like it's possible to set that up using the Sublime API (sublimehq/sublime_text#3965). I tested it by hand and It Works On My Machine™.

This PR does not expose clone_view.

class TestNewWindow(DeferrableTestCase):

def tearDown(self):
yield 100
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you add a comment why the wait is necessary here and reference the upstream issue? We won't be able to remove this for a while until we drop compatibility with affected builds.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

@FichteFoll FichteFoll added this to the 1.4.1 milestone Feb 24, 2021
@Thom1729 Thom1729 merged commit ddf61ad into master Mar 15, 2021
@FichteFoll FichteFoll deleted the revert-scratchness-after-closing-view-or-window branch March 15, 2021 17:07
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.

Possible data loss bug in close_view and close_window, plus new clone_view

3 participants