From 00a505e41a67de9f1093353cf7591ebc71857862 Mon Sep 17 00:00:00 2001 From: Dave Grijalva Date: Sat, 22 Jun 2024 01:53:59 -0700 Subject: [PATCH] docs: Correct path to global tasks file (#13372) 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 --- docs/src/tasks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/tasks.md b/docs/src/tasks.md index 9db38ef88f..c35b7bbb5a 100644 --- a/docs/src/tasks.md +++ b/docs/src/tasks.md @@ -32,7 +32,7 @@ There are two actions that drive the workflow of using tasks: `task: spawn` and Tasks can be defined: -- 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. +- 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. - 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`. - on the fly with [oneshot tasks](#oneshot-tasks). These tasks are project-specific and do not persist across sections. - by language extension.