Translate
Appearance
Text
This page always uses small font size
Width
AllSession Environment Variables
Translate to Iñupiatun
Translation of the wiki page Session Environment Variables from English (en).
This tool does not work without JavaScript. JavaScript is disabled, failed to work, or this browser is unsupported.
Translations:Session Environment Variables/Page display title/ik
Session Environment Variables
You need translation rights to translate messages.Get permission
Loading...
Latest updatesAll changes
Suggestions
In other languages
Need more help?Ask for more information
Translations:Session Environment Variables/1/ik
== Setting Session Environment Variables ==
You need translation rights to translate messages.Get permission
Loading...
Latest updatesAll changes
Suggestions
In other languages
Need more help?Ask for more information
It is simple to set environment variables that affect your whole session. Plasma will execute any script it finds in <tt>$HOME/.config/plasma-workspace/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/.config/plasma-workspace/env/path.sh</tt> with a contents similar to this:
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>$HOME/.local/bin</tt>). Finally you see the $PATH variable itself - that's because you want to add your new path into it, not replace the existing path.
{{Warning|If you want to point your home don't use '~', use $HOME instead}}
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:
You can also check how Plasma actually does it. KDE startup is complicated, it ends up calling either <tt>/usr/bin/startplasma-x11</tt> or <tt>/usr/bin/startplasma-wayland</tt>. If you are interested in reading the code, you can can view [https://invent.kde.org/plasma/plasma-workspace/-/blob/master/startkde/startplasma.cpp#L258 the startkde code online]; search for ''environment variables''.
== See also ==
{{Menu|System Settings|Startup and Shutdown|Autostart}} shows what scripts and applications run and lets you add new ones; see [[Special:myLanguage/System Settings/Startup and Shutdown|Startup and Shutdown]].
Loading messages...
0% translated, 0% reviewed
Retrieved from "https://userbase.kde.org/Special:Translate"