#LingCoder

A Geany / VS Code-style IDE for the Ling language - written entirely in Ling, in the LingStationX look: the egui-dark chrome, the ROYGBIV menu keys, the crosshatch-and- corner-brackets design system, and the Ling Dark editor colours from editors/vscode-ling.

#Run it

run.bat                     (Windows; logs to lingcoder.log)
ling run --interp ling/main.ling      (anywhere)

run.bat looks for ..\ling\target-coder\release\ling.exe (a web-feature build: silent background jobs), then ..\ling\target\release\ling.exe, then ling on the PATH. Open a folder with Ctrl+Shift+O (or pass it on the command line: run.bat C:\my\project).

#What's inside

• Explorer - file tree with context menus (new / rename / duplicate / delete / reveal)
• Editor - Ling Dark syntax colours (Ling, TOML, Markdown, JSON, cfg, shell), multi-tab, full selection editing, undo/redo, duplicate/move lines, toggle comment, indent guides, the live Ling lint with squiggles, find/replace (Ctrl+F / Ctrl+H)
• Search - find in files across the folder (Ctrl+Shift+F)
• Go - go to file Ctrl+P (with :line), go to line Ctrl+G, command palette Ctrl+Shift+P
• Run - run file F5, run project Ctrl+F5 (reads Ling.toml entry=), build F7, stop Shift+F5; output streams into the bottom panel, --> error lines are clickable
• Problems - the Ling lint, click to jump, F8 cycles
• Extensions - plain Ling files in extensions/, hot-reloaded on save, with commands, panels, events and the editor's right-click menu. See docs/EXTENSIONS.md (Help > Extension API) and Tools > New Extension...
• Claude - the bundled flagship extension: a chat panel on the activity bar (or a full chat tab - the window icon in its header) that knows your current file / selection / problems (toggle the chips), streams replies, and puts Insert / Copy on every code block plus a copy button on every message. Quick actions: Ctrl+K asks about the selection; Explain / Fix / Refactor / Comment are in Tools and the palette.
  With the tools chip on, Claude can read files, list folders, open tabs, write files and run commands - every run/write waits for your Allow / Deny in the panel (reads inside the project are automatic). Commands are platform-aware (cmd.exe on Windows, sh elsewhere, no shell on LingOS), and miao ... is routed to the real miao launcher - Claude is told to never use git in a temple.
  Set your key in Settings (Ctrl+,) or the ANTHROPIC_API_KEY environment variable. Requests go through curl in a background job; the key is passed in a local curl config file, never on the command line.
• Miao - the temple-of-versions panel (sidebar or full tab): live repo stats (soul, head rite, altar, keeper) read straight from .miao, and every ceremony as a button - divine, offer, rite (with message), lineage, yinyang, souls, summon, harmonize, talisman, pilgrimage, tribute, fair, chronicle ... The miao program is found in ../ling-source (override with miao_home= in settings.txt) and works on any folder holding a temple.

Keyboard reference: F1. Settings live in settings.txt; unsaved work is autosaved to cache/autosave/ every minute and offered back after a crash.

#Building a distributable

cd ling-coder && ling build . --platform win --out dist

(The manifest uses the portable launcher, so ling/ ships next to the exe.)