Support opening `.code-workspace` files to open vs code type workspace directly

[avp1598]

Check for existing issues

• [X] Completed

Describe the feature

I want to be able to open .code-workspace file which opens the workspace with all the folders defined in the file. The file looks something like this

{
  "folders": [
    {
      "name": "ⵣ protocol",
      "path": "."
    },
    {
      "name": "⛓️ blockchain",
      "path": "golang/blockchain"
    },
    {
      "name": "😈 daemon",
      "path": "golang/tribesd"
    },
    {
      "name": "🦀 client",
      "path": "rust/client"
    },
  ],
  "settings": {
    "editor.tabSize": 2,
    "files.exclude": {
      "**/build": true,
      "**/node_modules": true
    },
    "solidity.packageDefaultDependenciesContractsDirectory": "src",
    "solidity.packageDefaultDependenciesDirectory": "lib",
    "solidity.formatter": "forge",
    "solidity.compileUsingRemoteVersion": "v0.8.20",
    "git.detectSubmodules": false,
    "rust-analyzer.showUnlinkedFileNotification": false,
    "rust-analyzer.cargo.target": "wasm32-unknown-unknown",
    "rust-analyzer.inlayHints.chainingHints.enable": false,
    "rust-analyzer.inlayHints.typeHints.enable": false,
    "rust-analyzer.inlayHints.parameterHints.enable": false,
    "editor.codeActionsOnSave": {
      "source.fixAll.eslint": "explicit"
    },
    "editor.formatOnSave": false
  }
}

If applicable, add mockups / screenshots to help present your vision of the feature

No response

[atljoseph]

This is mainly why zed didn’t “stick” for me. What’s the point in being super fast as an editor if you have to have a different window open for each repo OR have to manually reopen the correct folders on startup? It works ok if you always open same set of folders, but not if you have multiple “workspaces”, as vscode refers to them. Project, workspace, whatever is called… it’s a user friendly shortcut that saves mental bandwidth for heavy users.

[saminton]

This is mainly why zed didn’t “stick” for me. What’s the point in being super fast as an editor if you have to have a different window open for each repo OR have to manually reopen the correct folders on startup? It works ok if you always open same set of folders, but not if you have multiple “workspaces”, as vscode refers to them. Project, workspace, whatever is called… it’s a user friendly shortcut that saves mental bandwidth for heavy users.

Same here, seeing as .code-workspace files are for vscode and can have the list of plugins etc. which won't be relevant, having say a .zed-workspace or .zed-project etc. would be fine imo.

[mloskot]

This is mainly why zed didn’t “stick” for me. What’s the point in being super fast as an editor if you have to have a different window open for each repo OR have to manually reopen the correct folders on startup?

Same here, for the exactly same reasons.

I often maintain multiple .vscode/*.code-workspace-s per project, especially multi-environment DevOps projects in single repo, for example: .vscode/env-dev.code-workspace, .vscode/env-prd.code-workspace, etc. each manually crafted with environment-specific configuration modules.

The simple zed . simply does not cut it.

[reslear]

use our config .zed/name.workspace and supports .vscode/name.code-workspace

1. folders same syntax

2. settings by proxy vscode -> zed: ex. "editor.fontSize": 13 -> "buffer_font_size": 13

ps. It's just an idea

[atljoseph]

Can you link the docs?

On Thu, Oct 10, 2024 at 8:12 AM reslear @.***> wrote:

use our config .zed/name.workspace and supports .vscode/name.code-workspace

1.

folders same syntax 2.

settings by proxy vscode -> zed: ex. "editor.fontSize": 13 -> "buffer_font_size": 13

— Reply to this email directly, view it on GitHub https://github.com/zed-industries/zed/issues/9459#issuecomment-2404923347, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF632FOAHVHRWLERC4SHW4TZ2ZVK3AVCNFSM6AAAAABPUPXHFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBUHEZDGMZUG4 . You are receiving this because you commented.Message ID: @.***>