Lately, I've been very inspired by @seninha's #X11 tools, especially #xmenu, #xfiles, and #xnotify:

https://github.com/phillbush

They're such a refreshing return to the core #UNIX #philosophy.

phillbush - Overview

[sẽˈnĩ.ə]. phillbush has 70 repositories available. Follow their code on GitHub.

GitHub

@morgant I'm glad you like them and find those tools inspiring! I'd love to know what they inspired you into... (is it the MLVWM confirmation dialog?)

XFiles controlker script uses xmessage by default, but you can disable it.I personally do not like xmesage. I have tried to use a XTerm window before as a confirmation dialog, so the user can type Y/N and press Enter; but that's not mouse-friendly.

@seninha Certainly a little inspiration for keeping `mlvwm-message`/`mlvwm-alert`/`mlvwm-confirm` dead-simple.

Beyond that, one thing that frustrates me about #MLVWM, and the ancient version of #FVWM it was forked from, is that menu configurations are static. I like your implementations of #xmenu & #pmenu piping menu definitions around dynamically.

I'll likely add a 'DynamicMenu' command, or something like that, which provides similar functionality... (1/n)

@morgant @seninha They don’t have to be dynamic though. Before fvwm gained dynamicmenu, you could always use +Test (x …) AddToMenu …

@thomasadam @seninha Thanks, that reminds me: one of the things on my #MLVWM #ToDo list is to review the `Menu` command implementation to see if multiple with the same name append, replace, or fail.

I also just noticed #FVWM’s `PipeRead`, which would solve the problem for Menus and more!

https://man.openbsd.org/fvwm#PipeRead

Though MLVWM doesn’t yet support `Read` within `Menu`.

fvwm(1) - OpenBSD manual pages