Merged
Conversation
This reverts commit 5c9fac0.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reverts #23
We'll add these back once the extension is actually merged to Zed.
Note
Low Risk
Low risk documentation-only change that doesn’t affect runtime behavior or shipped code.
Overview
Updates the README’s Zed section to instruct users to install the standalone
dexter-zedextension via the Extensions UI, replacing the previous claim that Dexter ships in Zed’s official Elixir extension along with the oldlanguage_serversJSON snippet.Also tweaks the wording around first-run behavior (index builds on startup) and reframes the
settings.jsonexample as the way to configure the Dexter binary path.Reviewed by Cursor Bugbot for commit 7feb463. Bugbot is set up for automated code reviews on this repo. Configure here.