Yesterday at 11:58pm, Jeremy C. Reed said:
> I agree it would be a good (default) option for the root image command not
> to be run.
>
> It is hard enough for most (many) users to figure out just to use
> bbkeys. I am sure that they have no idea about "nasty things".
>
> But, these newbie users do want to have a root image with their themes, so
> it should default to one standard root image command (like bsetbg).
>
> Maybe the rootCommand can be disabled and a new directive (component?)
> called "rootImage" that defines an image filename. This is could be used
> by a new .blackboxrc resource file configuration "ImageCommand" which
> defaults to bsetbg. Or it can be defined as:
> ImageCommand: xv -root -quit
> or Esetroot, xsetbg, display, wmsetbg, ...
>
> And another style directive could be "bsetroot" that defines the a
> bsetroot options.
>
> By adding one blackboxrc configuration and two style directives, the
> themes can have a default look even if the rootCommand is disabled.
I proposed such kind of thing some time ago. Indeed it is the best to
have not a generic shellcommand but something like:
backgroundType: image scale_max picture.jpg
or
backgroundType: gradient "flat gradient pipecross" black blue
or
backgroundType: solid darkslategrey
(The first parameter is a type id, the rest are params to define the
operation.)
Have just bsetbg take care what app is to be called to perform the
operation. bsetbg does that very fine.
As for 'damage when not running as root' I consider some evil rm -r ~/*
very dangerous. Of course, doing your daily work as root is not a good
idea.
wilbert
