I wonder why you list the window managers/desktop environments separately. One would think that all Arch-based distributions (“distros”) support most window managers anyway?
@tux0r I list them, so I know which distros emphasize which window Managers/Desktop
Environments. Generally distros provide excellent clues to learn from... As for sameness, it is difficult to achieve design & implementation objectives if you don't know how someone created a particular setup. New tools and tricks appear all the time.
und so geht es...oder?
I personally write-up what I learn and share it. Not everyone does that, though. I can assure you, it's Free and worth every penny. Seriously though, you are free to wander my writings to check the details and understand more of what I do with what I discover, assuming that is of interest.
I've been using bash since the 90's and I'm still a n00b. I'm still not constructing scripts in my head before I write them down. It's still
$ some command $ some command | more commands $ some command | more commands | even more commands
At some point I was making progress and I got to where this was happening:
$ some command $ some command | more commands $ even more commands $(some command | more commands)
Whatever I do, I still start with a very general command and add pipes. I don't know what I want before I see it.
I have recently started to rewrite some of my old scripts to get to the point earlier. It works when I'm writing in other languages, but in shell languages it's hard to get rid of this nasty habit of starting with the most general command and accumulate pipes.