On Sat, Feb 11, 2012 at 03:06:23PM -0800, Jason Timrod wrote:
Hi.
Having read the release notes for the new InfoStore command do I need to
convert any SetEnv commands to use it? I am not sure of why it exists, and
now why there's two different options to do much the similar thing
This should answer enough for you:
http://www.mail-archive.com/fvwm-workers@fvwm.org/msg02706.html
There's a distinct difference between options needing to be in the
environment for programs to operate (which is itself a bug, which I think my
post above alludes to, if not mentions, AFAICR), and bits of information
internal to FVWM which are useful to describe -- such as one's favourite
terminal program, or video player of choice, etc.
Previously to this, SetEnv was the only way to do this, which was far from
ideal. That's why I wrote InfoStore to do it instead -- which is slightly
cleaner than cluttering up FVWM's process space with environment variables.
The other motivation for it was to provide a generic way of adding labels to
FVWM without the need internally for those lables to have to form part of
the different parts of FVWM. So for instance, people have been wanting for
ages a way to use named colorsets, as in:
Colorset titlebarcs fg white, bg black
Now you can with:
InfoStoreAdd titlebarcs 0
Colorset 0 fg white, bg black
Style * HilightColorset $[infostore.titlebarcs]
... which also means you can reuse this information elsewhere in your
config, should it be applicable.
I could have implemented this with perllib, FWIW, but I do not want anything
in the core explicitly needing things like perl to operate.
If the information in my referenced email is lacking in the documentation
for InfoStore, feel free to submit a patch.
-- Thomas Adam
--
Deep in my heart I wish I was wrong. But deep in my heart I know I am
not. -- Morrissey (Girl Least Likely To -- off of Viva Hate.)
