Add script to install Zed inside the container #94
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.
In the interest of supporting more editors, this patch adds a script to install Zed. It would be nice for all of the most common editors to be supported, but certainly the Free ones should be included.
In general, I would love to know the stance of this project on including features like this. I don't use or have a licence for Sublime or CLion, although I would vote that this repository should support using them if somebody wants to submit a patch. That is, I think we should support the set of things that anybody might use, rather than the subset that everybody uses. For example, I am not a Vim/Emacs user, but I would see value personally if someone shared a good default configuration that worked in the container with clangd.
At the same time, I understand this might cause some dramatic scope creep / maintenance overhead.
In particular, for this PR, Zed requires workarounds in the container to get GPU access. For that reason, regardless of the result of the discussion above, I think this install script can be included without setting the precedent that every editor can be included.
This should land after the VSCodium PR. I didn't bother to duplicate that PR since I assumed any feedback on that PR would immediately apply here.