0669c96bdc
* Fix system notification command rendering as literal backtick (#318601) Terminal background-execution system notification labels wrapped the raw command in a single-backtick inline code span. Multi-line commands contain blank lines, which break an inline code span and cause the leading backtick to render literally instead of as code. Reuse the existing safe pattern (buildCommandDisplayText to collapse newlines and truncate, appendEscapedMarkdownInlineCode to fence safely) so the command always renders as inline code. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Simplify command display to first line + ellipsis (#318601) Replace newline-to-space collapsing in buildCommandDisplayText with first-line-only behavior: keep only the first line and append an ellipsis when the command spans multiple lines (or when the first line itself exceeds 80 characters). This is cleaner for UI labels than joining multi-line commands into a single long line of spaces. (Written by Copilot) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Scope first-line truncation to system notification site Revert the change to buildCommandDisplayText (it's used by other callers that expect the prior collapse-newlines behavior). Do the first-line + ellipsis truncation locally in _registerCompletionNotification where the system notification label is built. (Written by Copilot) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Extract buildCompletionNotificationCommand helper + tests (#318601) Move the first-line + ellipsis logic into a small exported helper next to the call site so it can be tested directly. Restore the trim/escape- artifact cleanup and 80-character truncation by running the first line through buildCommandDisplayText (which is a no-op for newlines once the input is already a single line). (Written by Copilot) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Use horizontal ellipsis character in completion notification Replace the three-dot "..." with the proper horizontal ellipsis character (U+2026) in buildCompletionNotificationCommand. Updated the truncation path to slice to 79 chars + 1-char ellipsis so the total length remains 80. (Written by Copilot) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Visual Studio Code - Open Source ("Code - OSS")
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, but 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
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 this project, for example:
- Submit bugs and feature requests, and help us verify as they are checked in
- Review source code changes
- Review the documentation and make pull requests for anything from typos to new content.
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:
- How to build and run from source
- The development workflow, including debugging and running tests
- Coding guidelines
- Submitting pull requests
- Finding an issue to work on
- Contributing to translations
Feedback
- Ask a question on Stack Overflow
- Request a new feature
- Upvote popular feature requests
- File an issue
- Connect with the extension author community on GitHub Discussions or Slack
- Follow @code and let us know what you think!
See our wiki for a description of each of these channels and information on some other available community-driven channels.
Related Projects
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 repositories are separate from each other. 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 (inline suggestions, 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 extension provides rich language support for JSON.
Development Container
This repository includes a Visual Studio Code Dev Containers / GitHub Codespaces development container.
-
For Dev Containers, use the Dev Containers: Clone Repository in Container Volume... command which creates a Docker volume for better disk I/O on macOS and Windows.
- If you already have VS Code and Docker installed, you can also click here to get started. This will cause VS Code to automatically install the Dev Containers extension if needed, clone the source code into a container volume, and spin up a dev container for use.
-
For Codespaces, install the GitHub 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 a 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.