The documentation lists the path to the global tasks config file as `~/.config/tasks.json`, but it's actually `~/.config/zed/tasks.json`. Release Notes: - N/A
Unified · Split
| @@ -32,7 +32,7 @@ There are two actions that drive the workflow of using tasks: `task: spawn` and · 31 unmodified lines | ||
| 32 | 32 | |
| 33 | 33 | Tasks can be defined: |
| 34 | 34 | |
| 35 | −- in global `tasks.json` file; such tasks are available in all Zed projects you work on. This file is usually located in `~/.config/tasks.json`. You can edit them by using `zed: open tasks` action. | |
| 35 | +- in global `tasks.json` file; such tasks are available in all Zed projects you work on. This file is usually located in `~/.config/zed/tasks.json`. You can edit them by using `zed: open tasks` action. | |
| 36 | 36 | - in worktree-specific (local) `.zed/tasks.json` file; such tasks are available only when working on a project with that worktree included. You can edit worktree-specific tasks by using `zed: open local tasks`. |
| 37 | 37 | - on the fly with [oneshot tasks](#oneshot-tasks). These tasks are project-specific and do not persist across sections. |
| 38 | 38 | - by language extension. |