Open ellnix opened 2 months ago
The CLI for that would probably be
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)
clash fetch
uses)
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: