-
Notifications
You must be signed in to change notification settings - Fork 398
Global Settings
Global settings can be overwritten by command level settings. Use Global settings to change things for all commands, like themes and how windows open.
This changes the app that opens settings.json for editing (Global Setting)
Possible values are default, nano, vi, vim or any terminal based editor.
default opens settings.json in whatever app is registered as the default for extension .json
"editor": "vim",
would open ~/.shuttle.json in vim
This allows you to flag the shuttle.app to start automatically (Global Setting)
Possible values are true or false
This allows you to set the default terminal (Global Setting)
Possible values are Terminal.app or iTerm
This changes the applescripts for iTerm (Global Setting)
Possible values are legacy or stable or nightly
If terminal is set to iTerm this setting is mandatory
"iTerm_version": "legacy", targeting iTerm 2.14
"iTerm_version": "stable", targeting new versions of iTerm
"iTerm_version": "nightly",targeting only the nightly build of iTerm
This setting is ignored if your terminal is set to Terminal.app
This sets the Terminal theme for all windows. (Global Setting)
Possible values are the Profile names in your terminal preferences. iTerm ships with one Profile named "Default". OS X Terminal ships with several. To see the names see the preferences area of the terminal you are using.
In iTerm the profile names are case sensitive.
Please ensure the theme names you set are valid. If shuttle passes theme "Dagobah" and it does not exist in iTerm, shuttle's applescripts fall back to the default profile. In iTerm this profile is called Default.
If you have removed Default or renamed it shuttle may not open your command.
This setting can be overwritten by the command level "theme" settings
This changes the default action for how commands are opened (Global Setting)
Possible values are tab or new.
tab opens the command in the active terminal in a new tab.
new opens the command in a new window.
This setting can be overwritten by the command level "inTerminal" settings
This changes parsing ssh config. By default, Shuttle will parse your ~/.ssh/config file for hosts. (Global Setting)
Possible values are false or true
This will ignore hosts in the ssh config. (Global Setting)
Possible values are the hosts in your config that you want to ignore. If you had github.com and git.example.com in your ssh config, to ignore them you set:
"ssh_config_ignore_hosts": ["github.com", "git.example.com"],
This will ignore keywords in your ssh config. (Global Setting)
Possible values are the keywords in your ssh config that you want to ignore.