JuliaEditorSupport / JuliaEditorSupport/zed-julia
Support for detecting a "default" Julia environment without project structure
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 121
- Forks
- 19
- Avg merge
- 13h 44m
- Merged PRs (30d)
- 7
Description
This is a feature request that is derived from https://github.com/JuliaEditorSupport/zed-julia/issues/4#issuecomment-2282894402 and https://github.com/zed-industries/zed/issues/16102#issuecomment-2284239325:
In the development process of a technical project I very often DO NOT have full project structure of a Julia package containing
- a
srcdirectory - a project description
Project.toml - etc.
Instead I am using standalone Julia files that I want to test and develop in a "default" Julia environment, as installed on my computer. This feature request asks for the support of standalone Julia files with no project stucture and no dependency of specific package versions. The requested functionallity is basically comparable to the Python implemention of Zed.
@whiterock for your information
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked JuliaEditorSupport and Zed issues, then compare the existing Julia support with Zed's Python implementation referenced in the request. Done means standalone Julia files work in a default environment without project structure or dependencies tied to specific package versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia, rust
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100