88a41bedd3
The fork shipped renamed binary/bundle but the product name "Zed" was still
shown everywhere in the UI. Rename the display name to "Joule" (tagline
"Energy-metered agentic coding") while preserving every load-bearing reference.
Display renames (105 .rs files): release_channel display_name, welcome +
onboarding + ai_onboarding, macOS app menu (About/Hide/Quit), window titles,
About panel, settings UI, notifications, update/collab messages, system specs.
Bundle display name (crates/zed/Cargo.toml) -> "Joule" so CFBundleName / the
menu-bar name and the .app are "Joule" (identifier science.transaction.AgentJoule
and the agent-joule binary are unchanged).
Docs (223 .md): product prose Zed -> Joule, fence-aware (code blocks untouched).
Embedded assets (12 JSONC): // comments only.
Legal (4 files): product -> Joule, entity "Zed Industries, Inc." -> "Transaction
Science, Inc.", domain zed.dev -> openie.dev. NOTE: these are structurally Zed's
inherited terms and need a real legal review, not just a rename.
Deliberately PRESERVED (renaming would break the app): font aliases ("Zed Plex
Sans"/".ZedMono" in text_system + assets), HTTP header names (X-Zed-Predict-*),
zed:: action ids, app/bundle identifiers (dev.zed.Zed*, Zed-Editor-* product ids),
zed.dev URLs, ZED_* env vars, crate/package names, "Zed Industries" in non-legal
attribution, and the {zed,Zed} config-dir glob.
Signed + notarized + stapled as Joule.app, installed to /Applications, verified
(Gatekeeper: Notarized Developer ID, FH93XC2VRR). Caveat: test-code string
literals were renamed too, so some `cargo test` assertions may need updating.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
1.9 KiB
1.9 KiB
| title | description |
|---|---|
| Editing Code in Joule | Core code editing features in Joule including multi-cursor, refactoring, code actions, and language server integration. |
Editing Code
Joule provides tools to help you write and modify code efficiently. This section covers the core editing features that work alongside your language server.
What's in This Section
- Code Completions — Autocomplete from language servers and AI-powered edit predictions
- Snippets — Insert reusable code templates with tab stops
- Formatting & Linting — Configure automatic code formatting and linter integration
- Diagnostics & Quick Fixes — View errors, warnings, and apply fixes from your language server
- Multibuffers — Edit multiple files simultaneously with multiple cursors
How These Features Work Together
When you're editing code, Joule combines input from multiple sources:
- Language servers provide completions, diagnostics, and quick fixes based on your project's types and structure
- Edit predictions suggest multi-character or multi-line changes as you type
- Multibuffers let you apply changes across files in one operation
For example, you might:
- Rename a function using your language server's rename refactor
- See the results in a multibuffer showing all affected files
- Use multiple cursors to make additional edits across all locations
- Get immediate diagnostic feedback if something breaks
Related Features
- AI Features — Agentic editing, inline code transformations, and AI code completions
- Configuring Languages — Set up language servers for your project
- Key Bindings — Customize keyboard shortcuts for editing commands