vicious VS lain

It's from vicious widgets.

Widgets are typically obtained by either using widget collections, such a Vicious or Bling, by "extracting" them from other people's repos or by just writing them yourself. Note that, to customize awesome, you really do want to learn how to use the widget system, as otherwise, you'd be missing out on one of awesome's greatest strengths. Also, no, it doesn't matter which distro you use. They are almost always distro independent (except for maybe something like a package update notifier or something, as that really can't be done distro independently). It does however matter whether you use the stable release (4.3 as of now) or the current git master, as stable is about 3 years old while the git master is in very active development. Some of the cooler widgets may only work on the git master branch.

Also I found this https://github.com/vicious-widgets/vicious/blob/master/widgets/cmus_all.lua

https://github.com/vicious-widgets/vicious a well known repo with widgets you can take inspiration from

https://stackoverflow.com/questions/52634985/awesome-wm-os-execute-vs-afwul-spawn https://github.com/vicious-widgets/vicious/issues/74

I'm using https://awesomewm.org/ with the https://github.com/vicious-widgets/vicious for almost 9 years now. I did spent the first year (on and off of course) tweaking everything to my liking.

Welcome to AW! A few points that may come in handy. * Read awesome-git API documentation first. There are a lot of points about it. * Do not use io.popen https://awesomewm.org/apidoc/libraries/awful.spawn.html * Encapsulate business logic to user custom library and re-use code for your widgets. Remove it from rc.lua. * You can use producer-consumer pattern to create signals and add graphical widget listeners to it. https://github.com/raven2cz/awesomewm-config/blob/master/fishlive/status/archupdates.lua https://github.com/raven2cz/awesomewm-config/blob/master/themes/multicolor/theme.lua * nvidia: nvidia-smi --query-gpu=temperature.gpu --format=csv,noheader,nounits * Other basics mem, net, etc. looks here, sometimes is better to use library: https://github.com/lcpz/lain/tree/master/widget * optional: try to divide GUI graphical components (theme parts, and your custom libs) and business logic layer (rc.lua). After a few months, you won't know why and where you implemented it, and you need to keep it in order. Especially the initialization order of the components. Lua requires a strictly sequential order.

I'm quite confused how to implement the password function for lain imap widget (https://github.com/lcpz/lain/wiki/imap) - using pass (author recommends spm or pass) gpg (and not plain text).

Probably you're using some widgets made by someone else. I see you have a require "lain" in your rc so it's safe to assume you're using lain's widgets, found here: https://github.com/lcpz/lain I'm not familiar with them and currently I am not at the PC but in this file in the repo: https://github.com/lcpz/lain/blob/master/widget/bat.lua You can find this piece of code: bat_notification_critical_preset = { title = "Battery exhausted", text = "Shutdown imminent", timeout = 15, fg = "#000000", bg = "#FFFFFF" } Check out how it works and maybe add your own presets. Good luck.

You can read more in their wiki : https://github.com/lcpz/lain/wiki/bat

Lain: https://github.com/lcpz/lain