Allow CLI options in the file

[KittyGiraudel]

What about allowing --sass-convert, --no-update-notifier and --no-prompt to live in the configuration file rather than passing those as CLI options?

Ideally, I think we should have a single option: --config. Everything else should live in the configuration file.

What do you think?

[valeriangalliat]

Why not both?

Sometimes, you only want to tweak a configuration value for a single CLI call, and it's annoying to edit a file for this. BTW we have no way to configure everything with the CLI, but the above options are probably the more common for this "single call" use.

[KittyGiraudel]

Then let's allow both.

[KittyGiraudel]

Who takes it?

[KittyGiraudel]

@FWeinb Your move. :)

[FWeinb]

It is kinda hard to do that. The location of the config file can be specified by a command line option. So we have a chicken egg problem here.

[KittyGiraudel]

I don't understand the issue.

[valeriangalliat]

I don't understand either.

[FWeinb]

Maybe @valeriangalliat should take this. You wrote the config loading in the first place.

[valeriangalliat]

No problem, I'll do it this week-end (and perhaps I'll ran in the same issue as you, but I don't see the chicken egg problem right now).