Code: Select all
printf '<span background="%s">\t\t</span>\n' "$col"
Code: Select all
printf "<span background='%s'>\t\t</span>\n" "$col"
Code: Select all
printf '%s\n' "<span background='$col'> </span>"
Code: Select all
printf '<span background="%s">\t\t</span>\n' "$col"
Code: Select all
printf "<span background='%s'>\t\t</span>\n" "$col"
Code: Select all
printf '%s\n' "<span background='$col'> </span>"
https://lists.x.org/archives/xorg-annou ... 02494.html There is rgb-1.0.6 - latest AFAIK - contains rgb.txtMochiMoppel wrote:Yes, rgb.txt is less essential than it used to be and AFAIK some distros have ditched it altogether, but as long as Puppy keeps a copy and as long as some applications use it, it should be accurate, shouldn't it? Keeping an outdated copy that was created 20 years ago (acc, to its header) in modern Puppies like bionicpub just makes no sense to me.
Symlinks /etc/X11/rgb.txt and /usr/lib/X11/rgb.txt added to woof-ce.MochiMoppel wrote:But apart from the content there is another issue that needs fixing:
Location of rgb.txt
Puppy default
the usual path to the file in Puppies is /usr/share/X11/rgb.txt, a location where no application I know would expect it.
netpbm utilities
The netpbm utilities expect rgb.txt to be in any of these locations:
/usr/lib/X11/rgb.txt
/usr/openwin/lib/rgb.txt
/usr/X11R6/lib/X11/rgb.txt
For reasons I don't know the devs didn't solve this issue by putting a symlink to /usr/share/X11/rgb.txt into one of these locations. Instead they tried to fix it with an entry in /etc/profile:yadCode: Select all
#w468 netpbm utilities need to be told where rgb.txt is... [ -f /usr/share/X11/rgb.txt ] && export RGBDEF=/usr/share/X11/rgb.txt
For yad the default path is
/etc/X11/rgb.txt
With a symlink in this location the commandwould create a yad dialog with rgb.txt as its palette.Code: Select all
yad --color --palette
gcolor2
Like yad gcolor2 shows rgb.txt by default, but searches in additional locations:
/usr/X11R6/lib/X11/rgb.txt
/usr/lib/X11/rgb.txt
/etc/X11/rgb.txt
/usr/openwin/lib/X11/rgb.txt
Unlike yad gcolor2 does not allow user defined alternative paths, hence woof-CE's strange decision to allow the misuse of /root/.rgb.txt for this purpose. A simple symlink in one of the paths known to gcolor2 would enable gcolor2 to function as intended.
Bottomline
A few symlinks would rectify all issues associated with the current location
Thank you.01micko wrote:Symlinks /etc/X11/rgb.txt and /usr/lib/X11/rgb.txt added to woof-ce.