Graphical launchers

Development reference · View source

The macOS app and the Linux application-menu entry start in your home directory in the configured mode. IDE and mux use the home workspace with integrated terminals. mode: editor stays in editor mode. Close a mux window and launch again to get back to the same persistent session. A host accepts one interactive frontend at a time.

In IDE and mux, if the graphical launcher receives files, the first file’s directory chooses the workspace. A directory argument chooses that directory. Editor mode opens files without a workspace, including new files whose parent directory doesn’t exist yet. Relative paths still start from the directory the launcher was started in. Files open with the same caret, duplicate-path and native-media rules as other window launches. Commands typed in a terminal still choose the workspace from the current directory. Finder file-open Apple Events are not integrated yet.

A startup refusal stays visible until you close the window. Invalid configuration shows its error using default presentation settings. The requested mode does not change, and workspace services do not start after a refusal. If the system can’t create a window at all, the error can only go to stderr.

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