I use a flat file with inline comments that is much easier to edit than XML, but it is still all in one file. The individual config tools just read / replace the appropriate lines. On the plus side it can be included in a shell script directly where XML would need to be parsed.MochiMoppel wrote:I never understood why we do now. Though fixmenus should only update the menu, in reality it updates the whole configuration file .jwmrc. This leads to the necessity of include files as safe havens for customized settings. JWM needs only 1 configuration file, and splitting this file into many include files certainly may have advantages, but I'm not sure if they outweigh the disadvantages. I tried this once and found that the small content for each include file doesn't justify the separation.technosaurus wrote:we don't need to regenerate keybindings and trays every time we update the menu
Did you consider to let fixmenus generate the menu only? In other words: Reduce the content of /etc/xdg/templates/_root_.jwmrc to <RootMenu> and rename the template to something like _root_.jwmrc-menu? The generated menu can then be included in .jwmrc - as the one and only include file.
I moved all the stuff from jwmrc-tray / personal / themes into my .jwmrc , thereby removing many duplicate and unneeded settings. I was surprised how small and neat a full featured and now editable .jwmrc can be. After all having only 1 configuration file (+ 1 include) is less confusing for novices and closer to what the JWM manual describes.
Yes menus will only generate their own xml, but now support an additional dynamic tag so technically it could be generated when the menu is hovered over. I did that with my 9menu version.