code-server/lib/vscode
Asher 5ebb096db5
Get terminals working
- Instead of a single listener per terminal that handles all events VS
  Code now has a single listener per event that handles that event for
  all terminals.
- Refactor Terminal to extend TerminalProcess to avoid duplicating
  methods. This required some modifications to TerminalProcess to access
  the pid and title and to set the ID.
- Remove our async change to shutdown. This was necessary to avoid
  disposing too early but shutdown already calls dispose so it turns out
  we didn't need to call it ourselves.
- Rename methods to match the command strings.
- Fix getting system shell (uses process.env).
- Use a single bufferer. Since it already supports buffering for
  multiple terminals there's no need to have one per terminal.
- Remove replay/reconnect logic. It's broken and unused so there doesn't
  seem much point in trying to refactor it to fit the changes right now.

While terminals work now there are still a lot of todos.
2021-04-13 16:35:13 -05:00
..
.devcontainer chore(vscode): update to 1.55.2 2021-04-09 11:32:27 +05:30
.github chore(vscode): update to 1.55.2 2021-04-09 11:32:27 +05:30
.vscode chore(vscode): update to 1.55.2 2021-04-09 11:32:27 +05:30
build chore(vscode): update to 1.55.2 2021-04-09 11:32:27 +05:30
extensions chore(vscode): update to 1.55.2 2021-04-09 11:32:27 +05:30
remote chore(vscode): update to 1.55.2 2021-04-09 11:32:27 +05:30
resources chore(vscode): update to 1.55.2 2021-04-09 11:32:27 +05:30
scripts chore(vscode): update to 1.55.2 2021-04-09 11:32:27 +05:30
src Get terminals working 2021-04-13 16:35:13 -05:00
test chore(vscode): update to 1.55.2 2021-04-09 11:32:27 +05:30
.editorconfig Merge commit 'be3e8236086165e5e45a5a10783823874b3f3ebd' as 'lib/vscode' 2020-12-15 15:52:33 -07:00
.eslintignore Ignore ipc.d.ts during VS Code lint 2021-04-02 11:12:13 -05:00
.eslintrc.json chore(vscode): update to 1.55.2 2021-04-09 11:32:27 +05:30
.gitattributes Merge commit 'be3e8236086165e5e45a5a10783823874b3f3ebd' as 'lib/vscode' 2020-12-15 15:52:33 -07:00
.gitignore Allow our server code to be tracked in git 2021-03-04 13:54:04 -06:00
.mailmap chore(vscode): update to 1.54.2 2021-03-11 10:27:10 -07:00
.mention-bot Merge commit 'be3e8236086165e5e45a5a10783823874b3f3ebd' as 'lib/vscode' 2020-12-15 15:52:33 -07:00
.yarnrc chore(vscode): update to 1.54.2 2021-03-11 10:27:10 -07:00
CONTRIBUTING.md Merge commit 'be3e8236086165e5e45a5a10783823874b3f3ebd' as 'lib/vscode' 2020-12-15 15:52:33 -07:00
LICENSE.txt Merge commit 'be3e8236086165e5e45a5a10783823874b3f3ebd' as 'lib/vscode' 2020-12-15 15:52:33 -07:00
README.md chore(vscode): update to 1.55.2 2021-04-09 11:32:27 +05:30
SECURITY.md chore(vscode): update to 1.55.2 2021-04-09 11:32:27 +05:30
ThirdPartyNotices.txt chore(vscode): update to 1.55.2 2021-04-09 11:32:27 +05:30
cglicenses.json Update to VS Code 1.52.1 2021-02-09 16:08:37 +00:00
cgmanifest.json chore(vscode): update to 1.54.2 2021-03-11 10:27:10 -07:00
coder.js Remove unused build import 2021-03-04 10:37:02 -06:00
gulpfile.js chore(vscode): update to 1.53.2 2021-02-25 11:27:27 -07:00
package.json fix(lib/vscode): package.json and yarn.lock 2021-04-09 11:54:28 +05:30
product.json chore(vscode): update to 1.55.2 2021-04-09 11:32:27 +05:30
tsfmt.json Merge commit 'be3e8236086165e5e45a5a10783823874b3f3ebd' as 'lib/vscode' 2020-12-15 15:52:33 -07:00
yarn.lock fix(lib/vscode): package.json and yarn.lock 2021-04-09 11:54:28 +05:30

README.md

Visual Studio Code - Open Source ("Code - OSS")

Feature Requests Bugs Gitter

The Repository

This repository ("Code - OSS") is where we (Microsoft) develop the Visual Studio Code product together with the community. Not only do we work on code and issues here, we also publish our roadmap, monthly iteration plans, and our endgame plans. This source code is available to everyone under the standard MIT license.

Visual Studio Code

VS Code in action

Visual Studio Code is a distribution of the Code - OSS repository with Microsoft specific customizations released under a traditional Microsoft product license.

Visual Studio Code combines the simplicity of a code editor with what developers need for their core edit-build-debug cycle. It provides comprehensive code editing, navigation, and understanding support along with lightweight debugging, a rich extensibility model, and lightweight integration with existing tools.

Visual Studio Code is updated monthly with new features and bug fixes. You can download it for Windows, macOS, and Linux on Visual Studio Code's website. To get the latest releases every day, install the Insiders build.

Contributing

There are many ways in which you can participate in the project, for example:

If you are interested in fixing issues and contributing directly to the code base, please see the document How to Contribute, which covers the following:

Feedback

See our wiki for a description of each of these channels and information on some other available community-driven channels.

Many of the core components and extensions to VS Code live in their own repositories on GitHub. For example, the node debug adapter and the mono debug adapter have their own repositories. For a complete list, please visit the Related Projects page on our wiki.

Bundled Extensions

VS Code includes a set of built-in extensions located in the extensions folder, including grammars and snippets for many languages. Extensions that provide rich language support (code completion, Go to Definition) for a language have the suffix language-features. For example, the json extension provides coloring for JSON and the json-language-features provides rich language support for JSON.

Development Container

This repository includes a Visual Studio Code Remote - Containers / Codespaces development container.

  • For Remote - Containers, use the Remote-Containers: Open Repository in Container... command which creates a Docker volume for better disk I/O on macOS and Windows.
  • For Codespaces, install the Visual Studio Codespaces extension in VS Code, and use the Codespaces: Create New Codespace command.

Docker / the Codespace should have at least 4 Cores and 6 GB of RAM (8 GB recommended) to run full build. See the development container README for more information.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

License

Copyright (c) Microsoft Corporation. All rights reserved.

Licensed under the MIT license.