Rename some config options

[Samq64]

Could gappih, axisbind and similar config options be renamed to be more intuitive? Maybe gaps_inner_x (much shorter than horizontal) and wheelbind (scrollbind could be confused with the layout, although touchpads do exist)?

[ItsLemmy]

I also believe all settings names should be revised while the project is still young and before it is too late.

Right now it's really a mixed bag:

• sometimes underscore is used, sometime it is not.
• sometimes settings are nicely prefixed by their scope (ex: blur_optimized) sometimes they are not (ex: enable_hotarea or ov_tab_mode)

I think having a cleaner config will helps a lot with early adoption of Mango.
But I can also understand if Mao Mao don't want to go thru this changes.

[Samq64]

In that case why not properly categorize the options into sections instead of prefixing them?

[Samq64]

Some improvements could also be made to the default configuration for newcomers such as adding spaces for readability and removing most of the tag rules so changing the default monitor layout works out of the box. Also, some of the default binds (middle click, Ctrl+Left/Right, Alt+[1-9]) conflict with common programs such as web browsers.

[DreamMaoMao]

These ununderlined options are basically inherited from dwl . To be honest, this project was initially just my personal dwl configuration, so the variable names were chosen very casually. But if there are significant changes now, it might cause trouble for those who are currently using it

[Samq64]

Publishing tagged releases to the AUR and other places where Mango is packaged could help with that to an extent but a lot of people probbably don't read the changelogs.

[ItsLemmy]

These ununderlined options are basically inherited from dwl . To be honest, this project was initially just my personal dwl configuration, so the variable names were chosen very casually. But if there are significant changes now, it might cause trouble for those who are currently using it

But IMO it's better to break everyone configs "once" rather than keep pilling up options this way. I have heard a few people mentioning that mango's config was too complex in comparison to others modern WMs and it was preventing them to even try it. Specifically the monitor "string definitiion" that is very hard to grasp.

I still believe a refactor of the settings with proper sections and names would be a huge help, but it's your call!

[Samq64]

Specifically the monitor "string definitiion" that is very hard to grasp.

So are you suggesting changing this:

monitorrule = DP-1, 0.50, 1, tile, 0, 1, 1080, 250, 2560, 1440, 165

to something like this?

[monitor]
name = DP-1
master_factor = 0.55
master_count = 1
layout = tile
transform = 0
scale = 1
position = 1080, 250
resolution = 2560, 1440
refresh_rate = 165

[ItsLemmy]

Yes that would be much nicer and easier to maintain and understand.

It can be a "INI file" like in your snippet or anything else: toml, yaml, etc...
This would also help to implement a proper settings validation method as requested in another issue.

The sub file includes would still need to work, as it's very important to keep a clean config.

[Samq64]

I think INI or toml are fine. I would prefer not to use a format that heavily depends on whitespace like yaml.