03 — Getting started
CLI reference
Every public editor argument and the exact startup behavior.
On this page
Syntax
| Input | Result |
|---|---|
| No path | Open the process current directory. |
| One path | Resolve the absolute root path. Quote paths containing spaces. |
| -- | Everything following is treated as a path, even if it starts with a dash. |
| -h / --help | Display help and exit 0 before loading UI/configuration. |
| -v / -V / --version | Display version and exit 0. |
| Unknown option or multiple paths | Usage error and code 2, unless help/version takes priority. |
oec [PROJECT]
openeditorcode [PROJECT]
oec --help
oec -h
oec --version
oec -v
oec -V
oec -- -projectPrecedence and limits
- Help takes priority over version and errors; version precedes argument validation. oec --help --unknown displays help and exits successfully.
- The parser does not validate that the path exists or is a directory. ~ depends on shell expansion.
- There are no --config, --theme, --readonly flags, multiple-file opening or line:column position arguments.
- Help, version and usage errors are printed to stdout. Saved language preferences are not loaded for help.
Public environment
OEC_CONFIG_DIR changes the global configuration directory. Without an override, Windows uses APPDATA and Linux uses XDG_CONFIG_HOME or ~/.config. OEC_INTERNAL_WORKER and OEC_NPM_LAUNCHER are internal details, not everyday user options.
$env:OEC_CONFIG_DIR = "C:\Users\you\oec-config"
oec "C:\Projects\My project"Chapter sources
Links pinned to the reviewed commit; they do not follow main.