Re: War on SetEnv -- hello, InfoStore.
Le Tue, 13 Dec 2011 07:24:05 +, Thomas Adam tho...@fvwm.org a écrit : I said there's no documentation for it yet. If you check, you'll note that the FVWM binary *is* built, since compiling the documentation happens *after* that point. -- Thomas Adam I added this file in doc/commands It is far from perfect, but it is the easiest way I can get portage to manage the installation. I prefer to have all the files in the system area to be managed by portage. It is far from perfect, but maybe you can use it as outline. Thank you again, Dominique Michel -- We have the heroes we deserve. InfoStore.xml Description: XML document
Re: War on SetEnv -- hello, InfoStore.
On 14 December 2011 17:36, Dominique Michel dominique.mic...@vtxnet.ch wrote: Le Tue, 13 Dec 2011 07:24:05 +, Thomas Adam tho...@fvwm.org a écrit : I said there's no documentation for it yet. If you check, you'll note that the FVWM binary *is* built, since compiling the documentation happens *after* that point. -- Thomas Adam I added this file in doc/commands It is far from perfect, but it is the easiest way I can get portage to manage the installation. I prefer to have all the files in the system I was never recommending you actually installed FVWM in that way, but if it makes your life easier, that's nothing bad. Your documentation is incorrect in that I now got two separate commands (InfoStoreAdd and InforStoreRemove) and that PrintInfo has its own section, etc., etc. -- Thomas Adam
Re: War on SetEnv -- hello, InfoStore.
Le Mon, 12 Dec 2011 11:02:00 +, 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.
Re: War on SetEnv -- hello, InfoStore.
On Mon, Dec 12, 2011 at 06:32:03PM +0100, Dominique Michel wrote: I can list the current values of all environment variables with the command env. Will it be possible to do something similar? No, but I can easily add it. -- 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.)
Re: War on SetEnv -- hello, InfoStore.
On Mon, Dec 12, 2011 at 05:39:38PM +, Thomas Adam wrote: On Mon, Dec 12, 2011 at 06:32:03PM +0100, Dominique Michel wrote: I can list the current values of all environment variables with the command env. Will it be possible to do something similar? No, but I can easily add it. Done. Please do a git pull and see: PrintInfo Infostore ... which will print its contents to stderr. -- 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.)
Re: War on SetEnv -- hello, InfoStore.
Le Mon, 12 Dec 2011 18:19:55 +, Thomas Adam tho...@fvwm.org a écrit : On Mon, Dec 12, 2011 at 05:39:38PM +, Thomas Adam wrote: On Mon, Dec 12, 2011 at 06:32:03PM +0100, Dominique Michel wrote: I can list the current values of all environment variables with the command env. Will it be possible to do something similar? No, but I can easily add it. Done. Please do a git pull and see: PrintInfo Infostore ... which will print its contents to stderr. -- Thomas Adam Thank you. I cannot get it to compile. Tried both by hand and with portage. Same result: xsltproc --path ../../doc --xinclude \ --stringparam profile.attribute output \ --stringparam profile.value html \ -o ImagePath.xml.p \ ./../docbook-xsl/profiling/profile.xsl ImagePath.xml make[3]: *** No rule to make target `InfoStore.xml', needed by `InfoStore.html'. Stop. make[3]: *** Waiting for unfinished jobs xsltproc --path ../../doc --xinclude \ --stringparam html.stylesheet ./../style.css \ --stringparam header.file ./../header.html \ -o IgnoreModifiers.html ./../fvwm.xsl IgnoreModifiers.xml.p rm IgnoreModifiers.xml.p xsltproc --path ../../doc --xinclude \ --stringparam html.stylesheet ./../style.css \ --stringparam header.file ./../header.html \ -o ImagePath.html ./../fvwm.xsl ImagePath.xml.p rm ImagePath.xml.p make[3]: Leaving directory `/var/tmp/portage/x11-wm/fvwm-/work/fvwm/doc/commands' make[2]: *** [all-recursive] Error 1 Dominique Michel -- We have the heroes we deserve.
Re: War on SetEnv -- hello, InfoStore.
On Mon, Dec 12, 2011 at 11:27:50PM +0100, Dominique Michel wrote: Le Mon, 12 Dec 2011 18:19:55 +, Thomas Adam tho...@fvwm.org a écrit : On Mon, Dec 12, 2011 at 05:39:38PM +, Thomas Adam wrote: On Mon, Dec 12, 2011 at 06:32:03PM +0100, Dominique Michel wrote: I can list the current values of all environment variables with the command env. Will it be possible to do something similar? No, but I can easily add it. Done. Please do a git pull and see: PrintInfo Infostore ... which will print its contents to stderr. -- Thomas Adam Thank you. I cannot get it to compile. Tried both by hand and with portage. Same result: xsltproc --path ../../doc --xinclude \ --stringparam profile.attribute output \ --stringparam profile.value html \ -o ImagePath.xml.p \ ./../docbook-xsl/profiling/profile.xsl ImagePath.xml make[3]: *** No rule to make target `InfoStore.xml', needed by `InfoStore.html'. Stop. make[3]: *** Waiting for unfinished jobs I said there's no documentation for it yet. If you check, you'll note that the FVWM binary *is* built, since compiling the documentation happens *after* that point. -- 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.)
