Starting Runyte

Development reference · View source

Command	What opens
`runyte`	The read-only about page
`runyte .`	The current directory in the explorer
`runyte file.txt`	That file
`runyte a.md src/main.rs`	Both files; the first is active
`runyte +12:4 notes.md`	`notes.md` with the caret on line 12, column 4
`runyte -- +draft.md -notes.md`	Files whose names start with `+` or `-`
`runyte --editor /etc/fstab`, `runed /etc/fstab`	That file in editor mode , with no workspace
`runyte --help`	Command-line options

Details:

Workspaces. runyte FILE opens the file in the workspace the current directory belongs to. Outside any workspace it refuses and suggests runyte --init DIRECTORY; use runed FILE to edit without one.
About page. A new persistent session starts on the about page too, so runyte -a before anything has been opened in that workspace shows it.
Several files. Runyte opens every text file given and leaves the first active. Editor and ide launches show a stable Opening workspace… screen while they load.
Editable at once. The first document frame is already editable. Syntax highlighting appears on its own when parsing finishes.
Caret position. Put a one-based +LINE or +LINE:COLUMN immediately before a file to place its caret when that buffer is first shown. Columns count Unicode characters, not bytes: runyte +12:4 "notes with spaces.md" src/main.rs.
Same file twice. Repeated spellings of the same resolved path share one buffer, at startup and later, in either mode. A save-as refuses a path already owned by another live buffer, including its resolved aliases; close that buffer before deliberately taking the path over.
Leading - or +. Put -- before such paths.
Binary files open the external-program prompt described in Opening binary files . Open them one at a time, so no explicit target can be silently skipped.
Standard input. runyte - (piped/stdin scratch input) is deliberately deferred: Crossterm owns stdin for terminal events. Before --, a lone - exits with an explanation instead of starting a terminal that cannot tell file contents from input events.

Inside the editor, press Space then ? for contextual help. See Help, hints, and the tutorial .