SAVE_CONFIG in separated file

[theophile]

@txigreman

There are also many ways to say things, and you response falls into the “not very polite” category.

Thanks anyway for your help, and sorry for wasting your time.

I think what he meant was that there are a lot of big plans for growing and extending Klipper in terms of functionality, so no developer is likely to spend time on reworking how the config files work unless and until there’s no other work to be done so they’re bored and looking for something to do. This is why @mykepredko asked “why adding complexity to the process is warranted.” Unless a requested feature is going to make a significant improvement for a significant number of users, it’s simply not going to get much traction.