Session Environment Variables/en: Difference between revisions
(Updating to match new version of source page) |
(Updating to match new version of source page) |
||
| Line 3: | Line 3: | ||
== Setting Session Environment Variables == | == Setting Session Environment Variables == | ||
It is simple to set environment variables that affect your whole session. KDE will execute any script it finds in <tt>$HOME/.kde/env</tt> whose filename ends in <tt>.sh</tt>, and it will maintain all the environment variables set by them. | It is simple to set environment variables that affect your whole session. KDE will execute any script it finds in <tt>$HOME/.kde/env</tt> whose filename ends in <tt>.sh</tt>, and it will maintain all the environment variables set by them. It is important that any variable you want to set must be also <code>exported</code>. In the case of PATH, for instance, your system will be set up with certain likely directories as the likely places to find things. Now you are adding an extra possible search place. You can see what is already set by opening [[Special:myLanguage/Konsole|Konsole]] and typing <code> echo $PATH</code> | ||
To add paths to your [http://en.wikipedia.org/wiki/Path_(computing) PATH], simply create a file named <tt>$HOME/.kde/env/path.sh</tt> with a contents similar to this: | To add paths to your [http://en.wikipedia.org/wiki/Path_(computing) PATH], simply create a file named <tt>$HOME/.kde/env/path.sh</tt> with a contents similar to this: | ||
| Line 10: | Line 10: | ||
}} | }} | ||
Let's explore that. The command ''export'' tells the system that this is something that should be saved and used when looking for files. Next you add the full name of the directory you want to add (in this case ~/local/bin, another way of writing /home/you/local/bin - again you can use <code>echo $HOME</code> to see how that works). Finally you see the $PATH variable itself - that's because you want to add your new path into it, not replace the existing path. | Let's explore that. The command ''export'' tells the system that this is something that should be saved and used when looking for files. Next you add the full name of the directory you want to add (in this case <tt>~/local/bin</tt>, another way of writing <tt>/home/you/local/bin</tt> - again you can use <code>echo $HOME</code> to see how that works). Finally you see the $PATH variable itself - that's because you want to add your new path into it, not replace the existing path. | ||
Often that will work well enough for you, but as you get more familiar with the system you will probably want to have the same environment when using a console or accessing your machine via '''ssh''', you will need to add to the end of your <tt>.bashrc</tt> something like this: | Often that will work well enough for you, but as you get more familiar with the system you will probably want to have the same environment when using a console or accessing your machine via '''ssh''', you will need to add to the end of your <tt>.bashrc</tt> something like this: | ||
| Line 18: | Line 18: | ||
}} | }} | ||
You can also check how KDE actually does it. It's done in your local <code>startkde</code>, which normally you can find in <tt>/usr/bin/startkde</tt>. If you are interested in reading the code, you can can view it [https://projects.kde.org/projects/kde/kdebase/kde-workspace/repository/revisions/master/entry/startkde.cmake | You can also check how KDE actually does it. It's done in your local <code>startkde</code>, which normally you can find in <tt>/usr/bin/startkde</tt>. If you are interested in reading the code, you can can view it [https://projects.kde.org/projects/kde/kdebase/kde-workspace/repository/revisions/master/entry/startkde.cmake online]. Just search the file for ''environment variables''. | ||
[[Category:System]] | [[Category:System]] | ||
Revision as of 16:41, 7 August 2011
Setting Session Environment Variables
It is simple to set environment variables that affect your whole session. KDE will execute any script it finds in $HOME/.kde/env whose filename ends in .sh, and it will maintain all the environment variables set by them. It is important that any variable you want to set must be also exported. In the case of PATH, for instance, your system will be set up with certain likely directories as the likely places to find things. Now you are adding an extra possible search place. You can see what is already set by opening Konsole and typing echo $PATH
To add paths to your PATH, simply create a file named $HOME/.kde/env/path.sh with a contents similar to this:
export PATH=$HOME/local/bin:$PATH
Let's explore that. The command export tells the system that this is something that should be saved and used when looking for files. Next you add the full name of the directory you want to add (in this case ~/local/bin, another way of writing /home/you/local/bin - again you can use echo $HOME to see how that works). Finally you see the $PATH variable itself - that's because you want to add your new path into it, not replace the existing path.
Often that will work well enough for you, but as you get more familiar with the system you will probably want to have the same environment when using a console or accessing your machine via ssh, you will need to add to the end of your .bashrc something like this:
source $HOME/.kde/env/path.sh
You can also check how KDE actually does it. It's done in your local startkde, which normally you can find in /usr/bin/startkde. If you are interested in reading the code, you can can view it online. Just search the file for environment variables.