Translations:Session Environment Variables/2/en: Difference between revisions

Latest revision as of 19:50, 22 February 2017

Information about message (contribute)

This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.

Message definition (Session Environment Variables)

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>

It is simple to set environment variables that affect your whole session. Plasma will execute any script it finds in $HOME/.config/plasma-workspace/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

Revision as of 20:50, 4 November 2016 view source FuzzyBot (talk \| contribs) 50,556 edits Importing a new version from external source		Latest revision as of 19:50, 22 February 2017 view source FuzzyBot (talk \| contribs) 50,556 edits Importing a new version from external source
Line 1:		Line 1:
	It is simple to set environment variables that affect your whole session. ~~KDE~~ 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>		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>