Le Mon, 12 Dec 2011 11:02:00 +0000, Thomas Adam <tho...@fvwm.org> a écrit :
> But people are forever asking me *why*, and it's because shoving > information in the environment is global to processes created from > FVWM within the same process group. Hence, that information is both > publicly viewable and potentially modifiable, which in some cases > might be what's wanted, but more than likely it isn't, and in that > case, what you're after then is some other means which can do the > same thing as SetEnv, but which is internal to FVWM, but still > accessible from things like functions [1]. > > This is why I wrote the InfoStore command. See: > > https://github.com/ThomasAdam/fvwm/tree/ta/metainfo Hi Thomas, That's a great news. Thanks a lot for that. > > I've not added anything to the docs yet, I've yet to psych myself up > enough to attempt that without injuring myself. But needless to say > it's a very simple linked-list implementation with two single entries > -- a key, and its value. Here's some examples: > > InfoStore key1 value1 > InfoStore key2 value2 > > To get the value for a given key, you must go through the FVWM expand > mechanism, as in: > > Echo $[infostore.key1] I can list the current values of all environment variables with the command env. Will it be possible to do something similar? I am not asking for a new feature because it will always be possible to debug a config using environment variables, and to shift using InfoStore when the debugging is done. Dominique Michel -- "We have the heroes we deserve."
