Awesome menu not configured about archinstall

[SkyyySi]

Digging around a bit, I found out about Arch's xdg-menu utility. It would be slightly simpler to maintain (since fewer lines are needed) and would provide a much more consistent solution across numerous window managers like Fluxbox, OpenBox or IceWM, not just awesome.

[SkyyySi]

Maybe changing the line

terminal = "xterm"

to

terminal = "alacritty"
webbrowser = "chromium"
filemanager = "nemo"

and changeing the part with

mymainmenu = awful.menu({ items = { { "awesome", myawesomemenu, beautiful.awesome_icon },
                                    { "open terminal", terminal }
                                  }
                        })

to

mymainmenu = awful.menu({ items = { { "awesome", myawesomemenu, beautiful.awesome_icon },
                                    { "open terminal", terminal },
                                    { "open web browser", webbrowser },
                                    { "open file manager", filemanager }
                                  }
                        })

is what you're looking for?

[Torxed]

Maybe changing the line

terminal = "xterm"

to

terminal = "alacritty"
webbrowser = "chromium"
filemanager = "nemo"

and changeing the part with

mymainmenu = awful.menu({ items = { { "awesome", myawesomemenu, beautiful.awesome_icon },
                                    { "open terminal", terminal }
                                  }
                        })

to

mymainmenu = awful.menu({ items = { { "awesome", myawesomemenu, beautiful.awesome_icon },
                                    { "open terminal", terminal },
                                    { "open web browser", webbrowser },
                                    { "open file manager", filemanager }
                                  }
                        })

is what you're looking for?

Exactly that :)
My main issue with awesome is that the LUA changes from time to time, so patch management is a PITA.

[SkyyySi]

I guess the simplest thing to do would be to have a diff patch included, it could be used by making a temporary copy of /etc/xdg/awesome/rc.lua, patching it, then creating the directory /etc/skel/.config/awesome on the target and moving the patched one there. Since awesome gets so few stable releases (4.3 was released over two years ago), it will probably be fine to do it that way.

[Torxed]

I guess the simplest thing to do would be to have a diff patch included, it could be used by making a temporary copy of /etc/xdg/awesome/rc.lua, patching it, then creating the directory /etc/skel/.config/awesome on the target and moving the patched one there. Since awesome gets so few stable releases (4.3 was released over two years ago), it will probably be fine to do it that way.

I like that idea, In general we should probably have something like archinstall.apply_patch(installation, patch_file_path, destination_file_path) for wrapping this functionality, It's needed else where too.

[Torxed]

That looks like a solid solution to the problem! Nice find!

[SkyyySi]

Also thinking about it, perhaps the changes could be put into an external file? Instead of patching the file at install and then leaving it, it could be put into a global directory and then be loaded from there. The only thing that would be required then would be to actually add the file load command itself, and those tend to not change. That could also be updated, but that would require a seperate package (it wouldn't be a good idea to install archinstall for something other than installing archinstall, would it?). It's questionable if that will work consistently for all WMs, but most should work.