Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion: Config / Configuration spec #175

Closed
7 of 23 tasks
elviskahoro opened this issue Sep 8, 2021 · 2 comments
Closed
7 of 23 tasks

Discussion: Config / Configuration spec #175

elviskahoro opened this issue Sep 8, 2021 · 2 comments

Comments

@elviskahoro
Copy link
Member

elviskahoro commented Sep 8, 2021

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:

Mac Native + UI + Appearance:

Visual Indicator upon some action:

Copy:

Shell

Keybindings: #30

Both: Config and Key Bindings

Running List (no associated issue)

  • autoclosing quotes/parenthesis in the command editor
@elviskahoro
Copy link
Member Author

elviskahoro commented Sep 8, 2021

A link to alacritty's default config.

Iterm GUI
Screen Shot 2021-09-08 at 7 09 20 PM

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).

@elviskahoro elviskahoro changed the title Config File / User Settings Design Configuration Spec -Running: Config File / User Settings Design Sep 10, 2021
@elviskahoro elviskahoro changed the title Configuration Spec -Running: Config File / User Settings Design Configuration Spec - Running: Config File / User Settings Design Sep 10, 2021
@elviskahoro elviskahoro changed the title Configuration Spec - Running: Config File / User Settings Design config: configuration spec - running list of related settings Oct 15, 2021
@elviskahoro elviskahoro changed the title config: configuration spec - running list of related settings Running: config / configuration spec Nov 4, 2021
@elviskahoro elviskahoro changed the title Running: config / configuration spec Idea: config / configuration spec Nov 8, 2021
@elviskahoro elviskahoro changed the title Idea: config / configuration spec Plugin: config / configuration spec Nov 8, 2021
@elviskahoro elviskahoro changed the title Plugin: config / configuration spec Discussion: Config / Configuration spec Nov 19, 2021
@warpdotdev warpdotdev locked and limited conversation to collaborators Nov 19, 2021
@Advait-M
Copy link
Member

Hey folks 👋 ! For anyone tracking this discussion - with respect to the point around syntax highlighting (Visual Indicator upon some action):

Super excited to let everyone know that we just launched Syntax Highlighting and Error Underlining on Warp yesterday 🎉 ! By default, Warp will highlight each part of a command in a different color denoting arguments, options/flags, variables, etc. and underline invalid commands with a dashed red line. You can toggle these features on/off via the Command Palette or Settings > Features.

Please download the latest release (v0.2022.10.11.08.13.stable_01) to get access to these features! The screenshot below shows the features in action:

Syntax Highlighting and Error Underlining Demo

Check out our user documentation for more details!

Let us know if you have any comments/feedback on these features!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants