Skip to content

docs: Overhaul Julia selection and server launch documentation - #76

Open
aviatesk wants to merge 1 commit into
mainfrom
avi/update-README
Open

docs: Overhaul Julia selection and server launch documentation#76
aviatesk wants to merge 1 commit into
mainfrom
avi/update-README

Conversation

@aviatesk

Copy link
Copy Markdown
Contributor

The README predated the direct julia -m JETLS launch and left key behavior undocumented: binary.arguments examples used a -- separator that was never explained, juliaup users had no documented way to select a Julia channel, and the runtime override and custom command examples were duplicated rather than organized by use case.

This change restructures the Julia selection and launch sections after the jetls-vscode README. The "Julia executable" and "Julia for JETLS" sections become use-case bullet lists covering juliaup channel selection (via direnv JULIAUP_CHANNEL and via binary.env.JULIAUP_CHANNEL) and direct executable selection (direnv PATH_add and JULIA_APPS_JULIA_CMD), each stating the launcher-resolution condition, the JETLS-only scope of binary.env, and the Windows executable caveat. The launch section now shows the exact managed launch command and explains the -- argument protocol, and the custom command section splits the user-managed binary and local checkout development cases into separate bullets.

The change also applies consistency and formatting cleanups across the file: version phrasing alignment, jsonc trailing-comma style, line-length rewraps, a reflow of the legacy REPL and plot side pane sections, and typo and grammar fixes.

The README predated the direct `julia -m JETLS` launch and left key
behavior undocumented: `binary.arguments` examples used a `--`
separator that was never explained, juliaup users had no documented
way to select a Julia channel, and the runtime override and custom
command examples were duplicated rather than organized by use case.

This change restructures the Julia selection and launch sections
after the jetls-vscode README. The "Julia executable" and "Julia for
JETLS" sections become use-case bullet lists covering juliaup channel
selection (via direnv `JULIAUP_CHANNEL` and via
`binary.env.JULIAUP_CHANNEL`) and direct executable selection (direnv
`PATH_add` and `JULIA_APPS_JULIA_CMD`), each stating the
launcher-resolution condition, the JETLS-only scope of `binary.env`,
and the Windows executable caveat. The launch section now shows the
exact managed launch command and explains the `--` argument protocol,
and the custom command section splits the user-managed binary and
local checkout development cases into separate bullets.

The change also applies consistency and formatting cleanups across
the file: version phrasing alignment, jsonc trailing-comma style,
line-length rewraps, a reflow of the legacy REPL and plot side pane
sections, and typo and grammar fixes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant