[opensuse] GUI for environment variables
Any suggestion regarding GUI tool to see the list and editing environment variables. KDE based tool will be nice. Thanks -- Soyuz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Well, that would be quite useless I guess. Viewer might make some sense, but editor would most probably not. To explain difficulty (well, next to impossibility) of such task you have to understand the way variables are set at shell start. Once shell process starts, it executes set of scripts. This script set varies depending whether the shell is login shell or not. And it may vary (and it does) between different shells too (there's bash, csh and many other shells). These scripts set the environment variables. 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. You can view e.g. /etc/bash.bashrc or /etc/profile to see that these scripts are not that simple and their output (set of variables and their values) may vary between users, shells etc. Cheers, Tosuja -- Petr "Tosuja" Klíma Mail: tosuja@tosuja.info Web: www.tosuja.info ICQ: 52057532 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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 ... either with options or not... without will list to stdout *all* current environment variables for the current shell. It would be a very simple matter of wrapping a PerlTK (or tclTK) gui wrapper around this command to list the variable names in a listbox, and then the value in an edit box... the result of the gui command would be to export the current "edited" list on to the next shell or next process... You could just as easily pipe the output of printenv to a sed|gawk routine, or perl script, or even grep, to pick out specific envs. Just some thoughts... -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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.
-- Kind regards,
M Harris <><
Randall Schulz
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. kai@jabba:~> 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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 05 June 2007 08:29, Randall R Schulz wrote:
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. Very clever... thanks!
... he can't say it isn't gui... :) -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 05 June 2007 12:51, M Harris wrote:
On Tuesday 05 June 2007 08:29, Randall R Schulz wrote:
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.
Very clever... thanks!
Very mildly clever...
... he can't say it isn't gui... :)
Well, in keeping with a contentious thread now many months in the past, I would. (Say it's not a GUI, that is.)
... M Harris <><
RRS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 05 June 2007 14:50, Randall R Schulz wrote:
... he can't say it isn't gui... :)
Well, in keeping with a contentious thread now many months in the past, I would. (Say it's not a GUI, that is.) Yeah, I suppose so...
... and in keeping with that, may I remind those of you who want to try Randall's cool desktop environment variable display tool that there are several ways to scroll down through the list... since the scroll-bar will not help you, and the list is quite long: ctrl + f will page forward ctrl + b will page backward (depending on your setup, the Page keys will work also) j will scroll down line at a time... k will scroll up line at a time... I suppose you could have the wrapper fire up emacs as well... but its a well known fact that real men use vi... so, there it is. -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, June 5, 2007 7:06 pm, M Harris wrote:
On Tuesday 05 June 2007 14:50, Randall R Schulz wrote:
      ... he can't say it isn't gui...  :)
Well, in keeping with a contentious thread now many months in the past, I would. (Say it's not a GUI, that is.) Yeah, I suppose so...
... and in keeping with that, may I remind those of you who want to try Randall's cool desktop environment variable display tool that there are several ways to scroll down through the list... since the scroll-bar will not help you, and the list is quite long:
ctrl + f will page forward
ctrl + b will page backward
(depending on your setup, the Page keys will work also)
j will scroll down line at a time...
k will scroll up line at a time...
Oh, neat!
I suppose you could have the wrapper fire up emacs as well... but its a well known fact that real men use vi... so, there it is.
<Kai stands up> "Hi, my name is, Kai." (from audience) "Hi, Kai!" "I am a Kate user and I don't know Vi." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Kai Ponte wrote:
...I suppose you could have the wrapper fire up emacs as well... but its a well known fact that real men use vi... so, there it is.
<Kai stands up>
"Hi, my name is, Kai."
(from audience) "Hi, Kai!"
"I am a Kate user and I don't know Vi."
Hey, Kai, I'm the ultimate blasphemer -- I'm an enthusiastic kate user, and I _do_ know vi :-). John Perry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 06/06/07, M Harris
Ok, these are for Kai... you have our pitty, but you are our friend.
Apparently you don't know kate though. No need for temporary files, just use kate -i to read from stdin. _ Benjamin Weber -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 06 June 2007 01:00, Benji Weber wrote:
Ok, these are for Kai... you have our pitty, but you are our friend.
Apparently you don't know kate though. No need for temporary files, just use kate -i to read from stdin. You are correct... in fact, I have never used kate. I think I dated her sister once...
... but seriously, I use VIM for all text editing. So, I'm learning about joe and kate and emacs... by the way... I knew there had to be a way to read from stdin with kate (but uffduh) I couldn't find it... :-P thanks! :) -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 2007-06-06 00:20, M Harris wrote:
On Tuesday 05 June 2007 21:13, Kai Ponte wrote:
<Kai stands up>
"Hi, my name is, Kai."
(from audience) "Hi, Kai!"
"I am a Kate user and I don't know Vi."
Ok, these are for Kai... you have our pitty, but you are our friend.
These desktop icon/scripts do not work here. A console window opens for a second and then closes. But if I manually run the command specified in the Exec= line in the file it launches Kate. A minor quirk -- Nohup coughs up a notice to the shell : nohup: ignoring input and appending output to `nohup.out' I modified the command to 1) redirect nohup's stdout/stderr to the bit bucket, 2) use the -i option for stdin reading with Kate, and 3) just cat the bash history file, since I usually have line numbers turned on in Kate. Exec=nohup bash -c "(cat ~/.bash_history) | kate -i " >/dev/null 2>&1 & Still, the command works fine run from a command line, but clicking on the icon doesn't run Kate. I removed the redirections to make nohup.out and this text appears in the file each time the desktop icon "executes" -- I gather it is from Kate: QObject::disconnect: Unexpected null parameter Any ideas? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 06 June 2007 22:31, Ken Jennings wrote:
On Wednesday 2007-06-06 00:20, M Harris wrote:
On Tuesday 05 June 2007 21:13, Kai Ponte wrote:
<Kai stands up>
"Hi, my name is, Kai."
(from audience) "Hi, Kai!"
"I am a Kate user and I don't know Vi."
Ok, these are for Kai... you have our pitty, but you are our friend.
These desktop icon/scripts do not work here. A console window opens for a second and then closes. But if I manually run the command specified in the Exec= line in the file it launches Kate.
...
Any ideas?
The "Run in terminal" option should be deselected (Properties -> Application -> Advanced Options). Also, the use of nohup and the detachment of the command (the ampersand at the end) are unnecessary. Those options were required in my originals because they used Vim. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 05 June 2007 06:29, Randall R Schulz wrote:
... 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.
Attached is a counterpart I use occasionally. It shows the accumulated BASH history. Randall Schulz
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
printenv | sort | kdialog --textbox /dev/stdin
To edit, could use some logic around
eval $(printenv | sort \
| kdialog --textinputbox Environment "$(http://linux01.gwdg.de/~pbleser/
/\\
* Mohammad Bhuyan
Any suggestion regarding GUI tool to see the list and editing environment variables. Yes, use gvim :) KDE based tool will be nice. AFAIK Gvim is not part of KDE toolset but it's well integrated. Guillaume -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (10)
-
Benji Weber -
Guillaume R. -
John E. Perry -
Kai Ponte -
Ken Jennings -
M Harris -
Mohammad Bhuyan -
Pascal Bleser -
Petr Klíma -
Randall R Schulz