Skip to content

Commit 8a9aa7e

Browse files
authored
docs: update Zed setup to use official elixir extension instead of fork (#32)
Zed extensions update path is a bit more complex than in other editors. It's: - [x] Update Extension itself - [x] Bump version - [ ] Update extension in registry [PR](zed-industries/extensions#5624) - [ ] Update docs [PR](zed-industries/zed#53793) - [ ] Release new Zed version Anyway, main changes are merged we're just waiting they propagate to the latest Zed release. Meanwhile I'm updating docs to use official repo instead of my fork.
1 parent b833c52 commit 8a9aa7e

1 file changed

Lines changed: 5 additions & 6 deletions

File tree

README.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -186,18 +186,17 @@ lspconfig.dexter.setup({})
186186

187187
### Zed
188188

189-
Zed support is available via a dev extension while the official Elixir extension PR is in [review](https://github.com/zed-extensions/elixir/pull/115).
189+
Zed support is available via a **dev extension** while the update for built-in [extension registry](https://github.com/zed-industries/extensions/pull/5624) and [documentation](https://github.com/zed-industries/zed/pull/53793) is being merged.
190190

191191
To install it:
192192

193-
1. Clone the repo and checkout the branch:
193+
1. Clone the official extension repo:
194194
```bash
195-
git clone https://github.com/flowerett/zed-elixir-extensions.git
196-
cd zed-elixir-extensions
197-
git checkout add-dexter-support
195+
git clone https://github.com/zed-extensions/elixir.git
196+
cd elixir
198197
```
199198
2. In Zed, open the command palette (`Cmd+Shift+P`) and run **zed: install dev extension**
200-
3. Select the cloned `zed-elixir-extensions` directory
199+
3. Select the cloned `elixir` directory
201200

202201
Once installed, enable it in your Zed `settings.json`:
203202

0 commit comments

Comments
 (0)