Discussion: Config / Configuration spec

[elviskahoro]

Describe the solution you'd like?

The Warp team is likely already thinking about this, but the two approaches I'm familiar with are Iterm's GUI with nested hierarchies and alacritty's config file. My intuition is that a config file will be easier to port across devices but may not be as accessible to new terminal users.

Options:
A: GUI (similar to Iterm)
B: Config File
C: Maybe a GUI that syncs directly to a config file. Any updates made directly to the config file will be updated in the GUI Preferences Pane.

Some ideas for each
A1. Syncing can likely be handled with our warp credentials, particularly for the enterprise version.
B1. The config file is lightweight, and you'd likely be serializing point A1 into some json or config file for syncing anyway. An explicit config file would help for offline interoperability. 

Would love some comments and suggestions on how the team and current beta users are thinking about this. Especially the arrangement of all the configurable settings in the case of a config file.

Is your feature request related to a problem? Please describe.

More so a design / product architecture question.
Relates to these issues

Tab Completion Settings: #39
Custom Completion Spec: #131
Keybinding Settings: #30
Prompt Settings: #96

Additional context

Github Features and Issues that imply having an accompanying configurable setting. Checked up to issue #174

Custom Triggers:

• Custom triggers #145

Mac Native + UI + Appearance:

• Menu bar instead of dock icon #92
• Ability to set default size for new windows #19
• Allow terminal input pane to be pinned to top (vs bottom) + ergonomics #22
• Setting for tab bar visibility #286
• DUP: Duplicate of #068 - Adapt to System Theme to account for dark and light switching #250
• Setting for hiding three dots #288
• Don't allow empty commands #287
• dim inactive split pane + focused / active pane should have a more prominent color scheme or indicator #304
• Resizing Tab - Make wider #313

Visual Indicator upon some action:

• Fish-like Syntax Highlighting - Highlighting existing and not existing commands #66
• Send a notification when a block is completed #71

Copy:

• Core: Copy on Select - Automatically copy text when highlighted #77
• UIUX: Only open URL when user clicks, allow selections on URL objects #138

Shell

• Ability to specify / change / configure warp to use different shell from system default. #132
• Configure default directory for new tab, new windows, new session, new pane #105
• Completions: suggestions while typing #52

Keybindings: #30

Both: Config and Key Bindings

• FZF Fuzzy reverse search via ctrl-r #167
• Via VIM-Mode: Moved to #579 - CTRL-N, CTRL-P to navigate lists #89
• Allow configuring which directory new tabs open #35
• Moved to #579: ENTER - Allow configuring whether enter executes command or inserts new line (CMD-ENTER to run) #73
• Option to insert the command currently highlighted in history dialog instead of running #314

Running List (no associated issue)

• autoclosing quotes/parenthesis in the command editor

[elviskahoro]

A link to alacritty's default config.

Iterm GUI

Option C, where the GUI and config file sync back and forth, would likely need a multitiered structure similar to the alacrity config as opposed to sublime for example (flat / one level).