Updating config file with new features #152
Replies: 5 comments 4 replies
-
When I add new config options I make sure the previous configs without them will have them at the default values, so it shouldn't be a big issue. I try to document all of them in release notes. |
Beta Was this translation helpful? Give feedback.
-
I'm not talking about default values and how Niri's work with them, but about how edit default values. For example, this commit, which will allow to change screen rotation. All new options need to be moved manually, right? |
Beta Was this translation helpful? Give feedback.
-
It's usually solved with putting the actual docs into separate place, like man page. |
Beta Was this translation helpful? Give feedback.
-
I agree with @kchibisov about new features documented in a man page. User configuration should not be touch at all. |
Beta Was this translation helpful? Give feedback.
-
Meanwhile, I made simple script for updating main config:
and
|
Beta Was this translation helpful? Give feedback.
-
There should also be an update mechanism for adding new lines and features to the user's configuration file. Otherwise, Niri use default config newer than the user has and user not warned about it.
Since this commit
Beta Was this translation helpful? Give feedback.
All reactions