ernesto1 / monochrome Goto Github PK

When no internet is available on startup, conky says there is 1 package available.
It seems the grep parsing is not solid.

The layout override is an advanced feature that should be optional.
The current setup forces the user's implicit knowledge of this feature.

Changes

• Use a flag to enable this feature: --layout-override 1920
• The launch script's default should be to launch the conkys using the x/y coordinates configured in their respective files. If a user wants to override this, they should make use of the layout override.
• Instead of tying the layout file name to a screen resolution, allow the user to specify their own "description" for it, ex. layout.<description>.cfg
• Ability to exclude a conky from launching from within the override file, ex. on laptop mode the external devices conky is not required

Current setup uses old configuration format. Adopt the new format.

• Prototype with USB devices
• Screenshot

There is no official way to tell the two window compositors (x11 and wayland ) that conky should reside on the primary monitor.

The xinerama_head setting allows you to choose which monitor conky should be displayed on. Unfortunately this setting behaves differently between the two compositors:

• x11 treats the primary monitor as 0
• Wayland has no concept of primary monitor. Monitors are listed from left to right starting at 0.

TODO

• Introduce an optional flag that allows the user to select what monitor they want: 1,2,3
• Have the launch script detect the window compositor at runtime and do a inline change to the conky files to the corresponding compositor equivalent, ex. under x11 monitor 3 would be 2 not possible to implement given how x11 and wayland treat monitors differently

When the conky setup is restarted, the prior running conky instances are killed as part of the cleanup step.
The prior instance of the bash script dnfPackageLookup.bash is not terminated however. This causes the script to be run again creating duplicating instances.

TODO kill any running instance of the DNF lookup script upon initialization

The extraction of the 5m load average fails once the system has been running for longer than 24 hours.
The output of uptime changes making our text parsing logic fail.

#                                                              1m    5m    15m
#  within a day     11:46:08 up 3 min,  1 user,  load average: 4.24, 2.49, 1.03
#  after a day:     22:54:03 up 2 days,  2:12,  1 user,  load average: 0.53, 1.16, 1.40

See dnfPackageLookup.bash

The launch script should run all conky jobs and the dnf package lookup in the background. Returning control to the shell.

Need to figure out how to get xargs to execute the commands in the background.

The new lua function to left pad the network up/down speed (commit 30f9e8b) is cutting the actual value by half, ex. if the speed is 1MiB, we get 500kib.

Additionally all native conky calls to the network speed (ex. ${totalup wlp4s0}) get halved as well. Even if they are not being parsed by the lua function. This affects the graph of said network interface as well.

This seems to be a bug with lua itself in the current version of conky I am on: v.1.11.5_pre