Qu

Editors

Syntax highlighting for the three editors people asked for, and a standalone environment if you would rather not configure anything.

Qu Studio

A desktop application that bundles the engine, so nothing needs installing separately. Editor, output pane, and figures rendered as you run.

Included

The engine, bundled

Qu Studio ships its own qu binary. Installing Studio installs a working Qu.

Included

Figures as you go

Plots render in the pane beside the code, and interactive mode redraws when the window changes size.

Included

Slash-command snippets

Type / for the common shapes — a filter, a spectrum, a figure set up for print.

Get Qu Studio

VS Code — notebooks

The second most-supported way to use Qu, on the strength of a real Jupyter kernel: not just syntax highlighting, a genuine persistent session.

Included

State survives across cells

One interpreter lives for the notebook's session — a variable set in one cell is visible in the next, the same session model as qu repl.

Included

No system libzmq

Speaks the real Jupyter wire protocol (ZeroMQ, HMAC-signed messages) over a pure-Rust implementation — nothing else to install.

Included

Figures inline

A plot in a cell renders inline as the cell's output, same as any other Jupyter kernel.

qu-jupyter install registers the kernelspec in the standard Jupyter data directory — VS Code's Jupyter extension discovers it the same way any other kernel is discovered. Open a .ipynb, pick Qu from the kernel picker. The same kernel works in JupyterLab and classic Jupyter too, not just VS Code.

Editor plugins

Each lives in editors/ in the repository. All three give syntax highlighting for .qu; the VS Code one also knows the builtin names. (For notebooks in VS Code, see the Jupyter kernel above instead — this is the plain syntax-highlighting-and-run-file extension.)

EditorPathInstall
VS Codeeditors/vscode-qu Copy the folder into ~/.vscode/extensions/ and restart.
Sublime Texteditors/sublime-qu Copy into Packages/User — Preferences → Browse Packages.
Notepad++editors/notepadpp-qu Language → User Defined Language → Import, then pick the XML.

Any editor at all. Qu files are plain text and the interpreter is one binary. qu run script.qu from a terminal is a complete workflow, and errors carry the line number.

Command line

qu run

Run a file

qu run analysis.qu

qu repl

A prompt

qu repl

--sandbox

Run untrusted code

qu run --sandbox theirs.qu

Network and writes denied; reads still work.