Repository navigation
launch arguments
Launchstation can cache a user argument list, consume a sidecar .arg file, or launch directly from a Text Editor buffer.
- Select a Text Editor-supported argument file.
- Open its operations menu and choose Use as launch arguments (Launch ELF with Args in the classic browser). The action appears only when the cursor is on a file that can be opened in the Text Editor.
- Launchstation parses and caches the argument lines in memory.
- Select the target ELF. The cached arguments are appended after the normal handoff path.
Both Text Editors always offer the action for the current in-memory document, including new, unnamed or unsaved buffers, arbitrary file extensions and documents whose backing file no longer exists. The current buffer supplies the arguments. Empty or invalid argument text is checked when the action is chosen.
For an ordinary ELF launch, Launchstation checks for a same-directory sidecar whose base name matches the ELF, for example:
APPS/
├── BOOT.ELF
└── BOOT.argIf arguments were already cached manually through the browser/editor action, the sidecar is ignored for that launch.
| Rule | Current limit |
|---|---|
| One non-empty line | One user argument |
| User arguments | 12 lines |
| Characters per argument | 255 |
| Total cached argument text | 2,048 bytes including terminators |
Line endings are stripped. Other characters on each line are preserved.
The target executable still receives the normal selected/handoff path as argv[0]; cached user lines follow it. External-core paths such as Neutrino build their own controlled argument set and do not consume a stray normal-ELF argument cache.
LAUNCHSTATION repository · Live documentation · Release downloads
Maintained from documentation sources. Do not edit generated pages directly; propose changes in the source repository.