Well, not only is wms not a wm per se, it's also not an original project. What is it then you ask. It's my implementation of some tools from the wmutils project in a **bunch of horrible shell scripts**. As a clear requirement, you should have the wmutils binaries. Namely:
This one is designed to maintain and incorporate from that one, things that are essential for my workflow. Also, this must contain future experiments around the configuration of my scripts.
I have been seeing computer users for years struggling to make the most of their equipment's resources against a delirious trend of uncontrolled software inflammation. The consumption of inflated programs with hollow utilities and pure aesthetics and the proliferation of redundant layers that turn the simplest task into a labyrinth of abstractions. I don't want the same for my private life. So I started removing and abandoning. In the last two years I have managed to get them back to me, time and energy. Things that I now use for my personal growth. \
Two great decisions that may seem like errors but are rather conditioning from which I cannot escape since in principle they move me towards their truth. To save: the use of Xterm as a term emulator is such an unorthodox launcher. \
The first choice is based on the fact that in many distros Xterm is installed together with Xorg and if not, it is the terminal emulator closest to Xorg as a project. I could use st or urxvt, but it would be moving towards another paradigm and breaking the conceptual homogeneity of this project. \
The second option is based on the extension of the first and the fact of using what is already installed. Since fzy/fzy is present in many scripts taking the place of a terminal menu, extending its operation and putting it in a resized terminal as a launcher is more than sensible. \
I have left the three main scripts, which are the ones I use daily, as the fundamental option. I've put the others, which are mostly experimental features, in a folder called opt, for optional.