dwmblocks VS bottom

Status bar : dwmblocks

dwmblocks: a clickable dwm statusbar written in c. would require some scripting and learning on your part. prob the only way you can get axactly what you are asking for outside of the look while remaining "suckless"

I just patched statuscolors to my dwm build with the aim of bringing colors to my statusbar (I use dwmblocks). I want to achieve something aesthetically similar to bumblebee-status, with each statusbar block appearing in a different color. As explained in the patch documentation, I defined an array of colors in my dwm config, something like this:

I use this https://github.com/torrinfail/dwmblocks, this will take care of slstatus stuff for you.

As of now, I have the official vanilla dwm, with just the statuscmd patch, AND vanilla dwmblocks from torrinfail, also with the statuscmd patch made for it. I'm having trouble understanding how to configure clickable modules.

At the moment in trying to patch the torrinfail version.

To update the status you can use a shell script see the suckless site. or use an external program such as dwmblocks.

Need suggestion on how are you restarting your dwm status bar set with xsetroot and not the classic dwmblocks. I have a script dwmbar which loads the status bar. Then I use another script which reloads the status bar whenever I press volume key, which takes significant time.

bottom

I'd suggest Bottom as a TUI alternative to the in-built task managers - https://github.com/ClementTsang/bottom

It works on Windows also.

If anyone is looking for a "top" like, written in Rust, might have a look at https://github.com/ClementTsang/bottom

Looks like bottom with another theme

bottom - A cross-platform graphical process/system monitor with a customizable interface and a multitude of features.

As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.