[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[],[],null,["The Cloud Shell Editor lets you manage your projects as workspaces.\nA workspace usually represents the root folder of your project and includes your\nproject-specific configuration files. A Home workspace (based on your Home\ndirectory) is created for you automatically.\n\nWith workspaces, you can specify persistent settings, run and debug\nconfigurations, and UI states (like open files) for all the folders in your\nworkspace.\n\nThis page explains how to create, open, save, and close a workspace, and\nconfigure Cloud Shell Editor and workspace settings.\n\nCreate a new workspace\n\nTo create a new workspace:\n\n1. Using the Cloud Shell terminal, create a new directory to use as your workspace:\n - Use `mkdir` to manually create a new directory\n - Use `git clone` to copy in an existing repository\n2. After your directory is ready, open it as a new workspace by clicking **File** \\\u003e **Open Workspace**.\n\nOpen a workspace\n\nYou can open a workspace in one of the following ways:\n\n- Click **File** \\\u003e **Open Folder**.\n\n- If no workspaces are open, click the **Open Folder** button in the\n Cloud Shell Editor Explorer view.\n\n- Select a recently opened workspace from the Recent section in the Welcome to\n Cloud Shell window.\n\n Alternatively, click **File** \\\u003e **Open Recent Workspace**.\n\nOpen a Home workspace\n\nTo operate using a Home workspace, open your Home directory as your workspace\nby clicking **File** \\\u003e **Open Folder** and then choose your Home directory.\n\nSave a workspace\n\nAfter you've added project folders to your workspace and configured it, you can\nsave your workspace under a new name by clicking **File** \\\u003e\n**Save Workspace As**.\n\nClose a workspace\n\nTo close your workspace, click **File** \\\u003e **Close Folder** and then click\n**OK** when prompted.\n\nDelete a workspace **Warning:** These actions will delete your folder and can't be undone.\n\nTo delete the folder, run the following command: \n\n rm -rf \u003cvar translate=\"no\"\u003eFOLDER_NAME\u003c/var\u003e\n\nConfigure settings\n\nThe Cloud Shell Editor's behavior and interface are easily configured\nwith the Settings menu. You can define your preferences for debugging\nconfigurations, YAML editing support, and Command Palette history limits, among\na variety of settings using this Settings editor. Settings are accessible\nthrough the Settings Gear\n, in the bottom\nleft corner of the editor.\n\nThere are three scopes for settings:\n\n- **User settings**: Globally-applicable settings, applied to all your instances of the Cloud Shell Editor. This configuration is stored in the browser.\n- **Remote settings**: Globally-applicable settings, applied to all your instances of the Cloud Shell Editor. These settings are stored in your Cloud Shell home directory under $HOME/.codeoss/data/Machine/settings.json.\n- **Workspace settings** : Workspace-specific settings, applied to only the active workspace. These settings are saved in the .codeoss/settings.json file in your workspace folder and can be shared using [version control](/shell/docs/version-control) or by [downloading](/shell/docs/uploading-and-downloading-files) the workspace folder.\n\n| **Note:** When a setting is set in more than one scope remote settings override user settings, and workspace settings override both remote and user settings.\n\nTo search for a setting, you can use the **Search Settings** search bar that\nreturns a set of settings that match your query, filtering out those that\ndon't relate to your criteria. The settings themselves can be set either by\nfilling in the input field, choosing an option from a dropdown menu, or\ntoggling a checkbox."]]
。