collapse awesome configs back into a smaller amount of files #3

New Issue

Open

opened 2023-05-02 00:28:21 +00:00 by nu · 1 comment

nu commented

2023-05-02 00:28:21 +00:00

Owner

i don't think this modularization approach is working quite like i'd like it to. it makes things seem needlessly complex, probably doesn't help that i'm not super well-versed in lua

i think some modularization should be good for organization purposes but it needs to be much less split up than it is right now

i don't think this modularization approach is working quite like i'd like it to. it makes things seem needlessly complex, probably doesn't help that i'm not super well-versed in lua i think some modularization should be good for organization purposes but it needs to be much less split up than it is right now

nu added the

(awesome)

label 2023-05-02 00:30:48 +00:00

nu added the

improvement

label 2023-05-02 00:36:54 +00:00

nu referenced this issue

2023-05-02 00:41:59 +00:00

awesome config is ignoring layout settings #4

nu commented

2023-05-02 00:48:32 +00:00

Author

Owner

binding/* can probably be merged into just one main/binding.lua file imo without causing issues with organization, as long as the resultant file gets commented properly

main/rules.lua and main/signals.lua can maybe also be merged into one main/clients.lua -- maybe main/layouts.lua and/or main/tags.lua can be included as well?

`binding/*` can probably be merged into just one `main/binding.lua` file imo without causing issues with organization, as long as the resultant file gets commented properly `main/rules.lua` and `main/signals.lua` can maybe also be merged into one `main/clients.lua` -- maybe `main/layouts.lua` and/or `main/tags.lua` can be included as well?