-
Notifications
You must be signed in to change notification settings - Fork 29.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
use monaco editor in terminal accessible buffer (#174400)
- Loading branch information
1 parent
524f422
commit 855ba20
Showing
12 changed files
with
146 additions
and
101 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
855ba20
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @meganrogge ,
I am importing VSCode 1.76.1 into Google and am trying to understand where xterm is going:
Terminal.registerBufferElementProvider()
Is the plan to remove this from VSCode again also, or is it coming back to xterm?
It would help me with my import to understand what I should expect.
Cheers
Ole
855ba20
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @rehmsen sorry for the confusion. We don't plan to have the buffer element provider in xterm.js anymore as it was just adding complexity unnecessarily. That dependency has since been removed in VS Code as well.
855ba20
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the explanation. We are importing the monthly released versions (and any .1... minor releases as they happen), and would prefer not to import xterm at head (as other internal projects also depend on xterm and I am not sure how stable the beta releases are). What are the plans for making a new 5.2.0 version for xterm? Is there any chance you could release a version of xterm when you make a vscode release, so that only vscode head depends on beta xterm, while vscode stable versions depend on xterm stable versions? I am not exactly sure how xterm is governed and whether that would be feasible at all, but as a user I think it would be nice if I could rely on a stable vscode version to have stable dependencies (which seems to mostly be the case right now - only node-pty and some xterm addons are depending on beta as of 1.76.1).
855ba20
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Tyriar can probably better answer this
855ba20
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rehmsen we maintain xterm.js as well, the beta tag just means it's released off of the master branch. The only "stability" that is added from a stable release of xterm.js is that we review the issues assigned to the milestones and then release. Node pty is in the same camp.
I wouldn't think of xterm.js/node-pty "beta" as being unstable, but rather an extension of the VS Code codebase; whatever version VS Code points at is probably very stable once it's been in insiders for a day or 2 and is even more so when VS Code is actually released (the one you import) as it's gone through VS Code's testing process.
855ba20
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We typically release xterm.js once every 1-3 months early in the month, because of the timing it's almost never aligned VS Code's release so almost every VS Code release has pointed at a "beta" xterm.js.