Toml config support with profiles

[hastinbe]

I’d like to propose adding optional TOML-based configuration with lightweight profiles to complement the current -m / -p workflow. I’m starting this as a discussion because I had already begun testing this feature before discovering the existing RawConfigParser support. Since that implementation appears to be kept primarily for legacy compatibility, I wanted to see if there is interest in a more modern, structured alternative.

Example usage and config:

# Use base config
bumblebee-status --config config.toml

# Use a profile
bumblebee-status --config config.toml --profile laptop

# Override theme from profile
bumblebee-status --config config.toml --profile work -t custom-theme

# Override modules from profile
bumblebee-status --config config.toml --profile work -m cpu memory

# Base configuration
theme = "solarized-dark"

[[modules]]
name = "cpu"
[modules.params]
format = "{load}%"

[[modules]]
name = "disk"
alias = "root"
[modules.params]
path = "/"
format = "{used}/{total}"

[[modules]]
name = "time"
[modules.params]
format = "%H:%M"

# Profile: laptop
[profiles.laptop]
theme = "solarized-dark"

[[profiles.laptop.modules]]
name = "cpu"

[[profiles.laptop.modules]]
name = "nic"
alias = "wifi"
[profiles.laptop.modules.params]
interface = "wlp3s0"

[[profiles.laptop.modules]]
name = "battery"

# Profile: work (extends laptop)
[profiles.work]
extends = "laptop"
theme = "gruvbox-dark"

[[profiles.work.modules]]
name = "cpu"

[[profiles.work.modules]]
name = "nic"
alias = "wifi"
[profiles.work.modules.params]
interface = "eth0"

[tobi-wan-kenobi]

That looks interesting and I'd definitely would welcome a PR!

I'm pretty relaxed about backwards compatibility, but if we can keep it, that's a plus.