Refactor River config #4

New issue

Open

opened 2025-02-06 19:49:44 +00:00 by Sunderland93 · 0 comments

Sunderland93 commented

2025-02-06 19:49:44 +00:00

Owner

There are several places where the River window manager configuration needs some improvement:

It is necessary to split the monolithic config into several smaller ones, for ease of configuration (general, input devices, output devices, autostart applications). Since the River's config is a shell script, this task will potentially be trivial.
Since the config is located in the user's home directory, this makes it impossible to make edits to it with the release of system updates (since the config is copied to the user's directory only when it is created). It is necessary to find a way to make the River config system-wide, while providing the user with the ability to add their own settings and scripts without interfering with the system-wide one. Since River does not officially have such support, thorough testing will be required.

There are several places where the River window manager configuration needs some improvement: 1) It is necessary to split the monolithic config into several smaller ones, for ease of configuration (general, input devices, output devices, autostart applications). Since the River's config is a shell script, this task will potentially be trivial. 2) Since the config is located in the user's home directory, this makes it impossible to make edits to it with the release of system updates (since the config is copied to the user's directory only when it is created). It is necessary to find a way to make the River config system-wide, while providing the user with the ability to add their own settings and scripts without interfering with the system-wide one. Since River does not officially have such support, thorough testing will be required.