computer (etc) displays and colour schemes – “black on white” or “white on black”?

I have “no idea”, what is better for my health: a dark (or black) background a light (or white) background I think, the human eye enjoys white as a “general background”, … – so I somehow think, white as background is “more enjoyable”. I just noticed, that my favourite editor has white as background and… Continue reading computer (etc) displays and colour schemes – “black on white” or “white on black”?

your OOXML file (“.docx”, “.xlsx”, “.vsdx”, …) and its “modified” timestamp

https://en.wikipedia.org/wiki/Office_Open_XML_file_formats https://github.com/JochenHayek/misc/blob/master/using_timestamps_in_filenames/create_snapshot_from_OOXML.sh https://en.wikipedia.org/wiki/XMLStarlet VSDX does not get listed as an OOXML conform file format, but for this purpose (here) we can treat it like one. Your “.docx” (or “.xlsx”) file is a ZIP file with a docProps/core.xml inside: $ unzip -l YOUR.docx … … docProps/core.xml … This is a convenient way to extract docProps/core.xml to… Continue reading your OOXML file (“.docx”, “.xlsx”, “.vsdx”, …) and its “modified” timestamp

shell command completion with busybox-w32 resp. its “ash”

With Bash command completion works the way, I expect it – or through all the years with Bash I learned what to expect: If I try to complete through a relativ or absolute directory, it lets me complete (sub)directory names and names of executable files. With ash (under busybox-32) initially I had trouble getting certain… Continue reading shell command completion with busybox-w32 resp. its “ash”

my 2017 Windows working environment

All these packages resp. utilities do not require Windows admin rights for getting them “installed” – actually they do not need “a Windows system installation”. Below C:\Users\jhayek I created a couple of subdirectories: opt: every package resp. utility has its own subdirectory below there bin: some .bat and .sh (BusyBox ash) scripts go there Packages resp. utilities:… Continue reading my 2017 Windows working environment

BusyBox’s “Almquist shell” is not as rich as the Bash

https://en.wikipedia.org/wiki/Almquist_shell https://linux.die.net/man/1/ash – the markup is in a terrible state https://en.wikipedia.org/wiki/Bash_(Unix_shell) The problems with “ash” always most evident, if a shell script got written to work with Bash and needs adapting / downgrading to the “ash”.