--===============1880520514581688207== Content-Type: multipart/alternative; boundary=20cf3074b92a1903bb04d6cb5673 --20cf3074b92a1903bb04d6cb5673 Content-Type: text/plain; charset=ISO-8859-1 I reported this bugreport for Kate: https://bugs.kde.org/show_bug.cgi?id=315853 I was instructed to ask here about the correct behavior of sourcing a script in .kde/env. It seems that Kate can't find anything that is sourced in .kde/env, even if the scripts there are sourced correctly by startkde. ++++++++++++++++++++++++++++++++++++ Kate Build plugin fails to use environment variables and PATH. If a script setting a variable or sourcing some script is put in .kde/env, Kate Build plugin cannot see the variables or programs set. Example: sourcing the following file #!/bin/sh source /opt/intel/mkl/bin/mklvars.sh intel64 source /opt/intel/composer_xe_2013/bin/compilervars.sh intel64 export PATH=$PATH:/home/tunguska/other_scripts should enable the intel compiler to be found by make and be used. Kate started from the menu can't see the compiler, but if Kate is started from the terminal with that script sourced, it can see the compiler correctly. Reproducible: Always Steps to Reproduce: 1. Put a script in ~/.kde/env to be sourced when the session starts. 2. Open Kate, configure the Build plugin to use make. 3. Use "Build" from Kate menu. Actual Results: make complains it can't find the executable set in the script. Expected Results: Call the executable (compiler) correctly. ++++++++++++++++++++++ Thanks for your time, PS: Please cc me as I'm not on the list. --20cf3074b92a1903bb04d6cb5673 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I reported this bugreport for Kate:

https://bugs.kde.org/show_bug.cgi?id=3D315853

I was instructed to ask here a= bout the correct behavior of sourcing a script in .kde/env. It seems that K= ate can't find anything that is sourced in .kde/env, even if the script= s there are sourced correctly by startkde.
++++++++++++++++++++++++++++++++++++
Kate Build plugin fails to use environment variables and PATH. If a script = setting a variable or sourcing some script is put in .kde/env, Kate Build p= lugin cannot see the variables or programs set.=20 Example: sourcing the following file=20 #!/bin/sh source /opt/intel/mkl/bin/mklvars.sh intel64 source /opt/intel/composer_xe_2013/bin/compilervars.sh intel64
<= span style=3D"color:rgb(46,52,54);font-family:'Open Sans','Helv= etica Neue',Helvetica,Arial,sans-serif;font-size:13px;line-height:22.39= 9999618530273px;white-space:pre-wrap;background-color:rgb(254,254,254)">exp= ort PATH=3D$PATH:/home/tunguska/other_scripts should enable the intel compiler to be found by make and be used. Kate star= ted from the menu can't see the compiler, but if Kate is started from t= he terminal with that script sourced, it can see the compiler correctly. Reproducible: Always Steps to Reproduce: 1. Put a script in ~/.kde/env to be sourced when the session starts. 2. Open Kate, configure the Build plugin to use make. 3. Use "Build" from Kate menu. Actual Results: =20 make complains it can't find the executable set in the script. Expected Results: =20 Call the executable (compiler) correctly.

++++++++++++++++++++++

Thanks for your time,

PS: Please cc me as I'm not on the list.
--20cf3074b92a1903bb04d6cb5673-- --===============1880520514581688207== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << --===============1880520514581688207==--