On Tue, June 5, 2007 6:29 am, Randall R Schulz wrote: > On Tuesday 05 June 2007 00:08, M Harris wrote: >> On Tuesday 05 June 2007 01:36, Petr Klíma wrote: >> > The caveat is that >> > many variables might be set dynamically based on informations read >> > from other config files. One can even include his own script >> > setting his own set of variables. Many do this. >> >> Yes... >> >> ... however, if what you are looking for (at a moment in time) is a >> listing of "current" environment variables you can use the command: >> >> printenv > > The attached desktop file will, when activated, open a window that > shows > the environment variables that will / would be in effect if you were > to launch an interactive BASH shell. > > You can modify its command to create variants, of course. > > I created and use it in KDE, so I'm not sure if Gnome will use it, but > I > have this vague sense that they use the same .desktop file format.
Thanks! I just installed that. In the past (going back to DOS 3.3 days) I would simply pipe the environment variables out to a text file. In that manner I can also save them by date - 20070604_kp_environment.txt - for example. [EMAIL PROTECTED]:~> set > 20070604_kp_environment.txt I've also thought about a gui program for environment variables. It would start as a YaST module. It would allow one to traverse the tree of environment variables. I would even think of breaking them up into sections, maybe calling them HIVES (hierarchical input variable environment settings) and then calling the program a - I dunno - registry. Yeah, that's it - I'm going to make a "registry" program for YaST! -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
