Happy Birthday VastOne

horn tooting smiley with confetti swirling . .
hello everyone

Hello VastOne and PackRat and everyone
Birth: -
"Unknown"
You get a date when here get a -.  (?)
In the 2014 post, VastOne stated count on two fingers [twice] in six years.  I will add here a since, once in seven years, to that.
The long story is, I got started with vsido around 2013live-2014install. one hdd failure i switched to Lite vsido and machine change.  Machine made it through two python/ perl escapades that, i did read, shut down a lot of machines. I was proud to make it through those ; But,, a xorg upgrade killed it later.  (RE)Installation brought machine to the xorg updates,,, and machine quit every time after the xorg upgrades. I switched install attempts between Lite and stock regular several times, finally got one to succeed with xorg and beyond.  here is the date of that re-install with stock vsido. now another python change in its history. An excuse for blather, thanks for the pointer to stat birth:date fun.   2019-10-31 11:26:51 
mail, apt, and dpkg logs begin that date 10-31., so i think that is it. (?) 
   

Thank you for vsido. 

herev@a1410y:~$ stat /var/log/installation.log
  File: /var/log/installation.log
  Size: 9559          Blocks: 24         IO Block: 4096   regular file
Device: 802h/2050d    Inode: 1317578     Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2021-01-19 17:35:22.035929581 -0700
Modify: 2019-10-31 11:26:51.839270806 -0700
Change: 2019-10-31 11:26:51.839270806 -0700
 Birth: -


Hello VastOne 
I hope, when the upgrade removes wicd, that you are not using it at the time. 
When upgrade removes medit, with what will you replace medit? 
.In with the new.  Readied for peril of mass removal. 

Looks; 
custom

VastOne 
Happy Birthday. 

hello PackRat. hi jedi. vsido one system on one machine rules with ... well only 1245 packges. not bigger than 3000. but for comparison , folks.

hello PackRat
hi jedi.  Have no idea why it works.  Here it is:
${color}key ${color7}state active
${color7}NumLock   ${exec xset q | grep Num |awk '{print "  " $8}'}
${color7}Caps Lock ${exec xset q | grep Caps |awk '{print "  " $4}'}

There is some kind of awk default to print, so somehow it could be shorter. what do you think? can it be shortened?
Without Your start at it I never could have got this. thanks.
There is alternate ways, better way?
Is it close enough to not be considered silliness?
Fingers- crossed here that you say it is ready to share. is it ready?  If not, then stop me here before it makes me look silly elsewhere please.  I will wish to include the code You passed along as the starting point. 

hello PackRat  and everyone
It started with a screencapture. It spun into disorientation looking through five years of conky.  Now left me in chagrin to re-find the recent jedi's 20180227a [/6V3nj] screencapture of February 22 shows conky with a keyboard key-state indicator.  finally found it again.  I do not know where best to post this : in screenshots February is past or in the conky thread.  I wish to know more about the key state indicator, please, jedi.  In the meantime I have convoluted a meager key indicator that does not look in conky so fantastic as that of jedi's screencapture. 
jedi. can You please send me in the right direction about that conky indicator? or show the code / script?  for key state.  seems useful for a machine that is without visual indicator.  how much resources does that eat?