History

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

Dave Grijalva committed 2 years ago

Commit 00a505e1 parent ed9f6e21 file · +1 −1Browse files

Unified · Split

docs/src/tasks.md+1−1
@@ -32,7 +32,7 @@ There are two actions that drive the workflow of using tasks: `task: spawn` and · 31 unmodified lines
32 32
33Tasks can be defined:33Tasks 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- 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`.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- on the fly with [oneshot tasks](#oneshot-tasks). These tasks are project-specific and do not persist across sections.37- on the fly with [oneshot tasks](#oneshot-tasks). These tasks are project-specific and do not persist across sections.
38- by language extension.38- by language extension.

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t