You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When considering things like #20 and various other features #60 we will require to maintain some sort of configuration state.
I made this issue to discuss the interface for it. Assuming that we store it in a toml file to be consistent with the rest of the repo, we will probably have simple key/value strings.
Personally I recommend a git-like syntax:
$ clash config
workspace: not set
editor: not set
$ clash config editor vim
Successfully set editor to vim.
$ clash config
workspace: not set
editor: vim
The text was updated successfully, but these errors were encountered:
clash config show [KEY] (default to printing the entire config file if KEY is not given)
clash config set <KEY> <VALUE>
clash config edit (create & open the config.toml file in $EDITOR, not 100% sure if this one is needed)
but to be honest at first stage we just need to have a file, the CLI is easy to add later. Here are the options the config file should contain (eventually, not everything needs to be implemented at once)
When considering things like #20 and various other features #60 we will require to maintain some sort of configuration state.
I made this issue to discuss the interface for it. Assuming that we store it in a
toml
file to be consistent with the rest of the repo, we will probably have simple key/value strings.Personally I recommend a
git
-like syntax:The text was updated successfully, but these errors were encountered: