Editor links
Every source reference on this site — written as inline code like
otp/lib/kernel/src/net_kernel.erl:100 — gets small links appended:
- gh — the file on GitHub, at that line. Only for repos with a public home.
- open — the file in your local editor, at that line. Needs the settings below, because the absolute path differs per machine.
Settings
Section titled “Settings”One field per repo. Leave a field empty to use the default shown as its placeholder. Stored
in your browser’s localStorage; nothing leaves the page.
How references are written
Section titled “How references are written”A reference always starts with a repo key, then the path from that repo’s root:
| Key | Repo |
|---|---|
talk |
This talk directory — code samples, pcaps, the epmd2 spec. No GitHub link. |
otp |
erlang/otp |
elixir |
elixir-lang/elixir |
libcluster |
bitwalker/libcluster |
netzlive.cluster |
The NETZlive clustering wrapper (private) |
redispatch |
NETZlive redispatch (private) |
netzkoordinator |
NETZlive netzkoordinator (private) |
netzlive |
NETZlive umbrella (private) |
user-management |
NETZlive user-management (private) |
Add a repo by adding it to REPOS in public/code-refs.js and to this table.
GitHub links point at the default branch, so line numbers drift. When a line number
matters, also note the tag or commit in the prose — otp at OTP-28.1.
URL schemes
Section titled “URL schemes”| Editor | Scheme |
|---|---|
| Zed | zed:///<abs-path>:<line> |
| Cursor | cursor://file/<abs-path>:<line> |
| VS Code | vscode://file/<abs-path>:<line>:1 |