Populate a default config file about bottom HOT 6 CLOSED

Ah, okay. Thought you meant something like, if you run say btm -a with no config file it would generate a config file with the average_cpu flag set to true.

Looks good then!

from bottom.

If you accept contributions I would like to tackle this issue, seems like a good first issue

from bottom.

Sure! I thought about doing this originally but wasn't sure what a good way to tackle this was.

from bottom.

The approach I have been using in my projects that use config files is the following:

• the program starts
• looks for a config file
  • if it exists, load the config
  • if it does not exist, create it with a ready config that has comments around each field (similar to alacritty) and load it
• overwrite the config with commandline flags
• use defaults for missing fields

What do you think?

EDIT: meant override, not overwrite

from bottom.

overwrite the config with commandline flags

While I like the idea behind this part, it's kinda 50/50 for me. I'm just not 100% on setting values for the user without them explicitly knowing that they're set, especially since if an option is set to true on the config file, then there's no way to actually turn the thing off from the command line - only on.

So either notifying the user what values are set, or just (imo the easier solution I guess) leaving it default entirely if we create one is probably what I would rather do.

The rest of it I like though.

from bottom.

What I meant by overwrite the config with commandline flags is what is already currently implemented. If my config file says the temperature should be Kelvin, but I run bottom with btm -c it will prioritize the Celsius flag and show the temperature in Celsius

from bottom.