upterm config edit
Edit the config file
Synopsis
Open the config file in your editor, first creating it, and its directory, from the example when there is none.
Config file: /home/user/.config/upterm/config.yaml
The editor is $VISUAL, else $EDITOR, else nano (vi without nano; notepad on Windows). A value that names an existing file runs as it is; any other is split into a program and its arguments (code –wait), as a POSIX shell would on Unix and by the Windows command-line rules on Windows.
Once the editor exits, the file is checked as commands read it: its YAML, its keys, and each value as the command it belongs to would check it. Each problem is one upterm: line, and the exit status is 1. When the editor itself exits with an error, the file isn’t checked.
Exit status: 0, or 1 on failure.
upterm config edit [flags]
Examples
# Edit the config file:
upterm config edit
# With an editor that needs an argument to wait:
VISUAL='code --wait' upterm config edit
Options
-h, --help help for edit
Options inherited from parent commands
--debug Enable debug logging (log file: /home/user/.local/state/upterm/upterm.log). A non-empty DEBUG turns it on too.
SEE ALSO
- upterm config - Manage upterm configuration