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

cache buffer to fix VS Code issue #111562 #3203

Merged
merged 1 commit into from
Jan 4, 2021
Merged

Conversation

meganrogge
Copy link
Member

@meganrogge meganrogge commented Jan 4, 2021

@meganrogge meganrogge changed the title cache buffer to fix #111562 cache buffer to fix VS Code issue #111562 Jan 4, 2021
@Tyriar Tyriar added this to the 4.10.0 milestone Jan 4, 2021
Copy link
Member

@Tyriar Tyriar left a comment

Choose a reason for hiding this comment

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

👍

@Tyriar Tyriar merged commit 4de6f1c into xtermjs:master Jan 4, 2021
Copy link
Contributor

@mofux mofux left a comment

Choose a reason for hiding this comment

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

Looking over the merged PR I think I found this not to be working as expected. Please see the comment for details.

@meganrogge @Tyriar

Comment on lines +62 to +65
if (!this._buffer) {
return new BufferNamespaceApi(this._core.buffers);
}
return this._buffer;
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this fix doesn't work because this._buffer is never assigned. I think it should have been:

if (!this._buffer) {
  this._buffer = new BufferNamespaceApi(this._core.buffers);
}
return this._buffer;

Copy link
Member Author

@meganrogge meganrogge Jan 4, 2021

Choose a reason for hiding this comment

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

yes you're absolutely correct. i'll create another pull request now to fix that.

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.

3 participants