KDevelop ignores enviroment variables that I set in Settings -> Configure Kdevelop -> Environment. Reproducible: Always Steps to Reproduce: 1. Go to Settings -> Configure Kdevelop -> Environment 2. Choose "default" environemnt. 3. Click "+" and add variable FOO with value bar 4. Open Konsole in kdevelop 5. Type echo $FOO Actual Results: Empty string is echoed. Expected Results: "bar" string should be echoed.
We are not forwarding the environment variables to the Konsole tool view. I wonder if we want that, though...
The problem was not only in konsole view - kdev-python plugin was not seeing these variables as well, namely PYTHONPATH. I would like see project environment variables apply globally for kdevelop and its plugins. For me it looks like a convenient way to define python environment per project. As a workaround I'm currently creating separate application launcher for each project which is by far less convenient. On 5 באוג 2013, at 21:57, Aleix Pol <aleixpol@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=322477 > > Aleix Pol <aleixpol@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |CONFIRMED > CC| |aleixpol@kde.org > Ever confirmed|0 |1 > > --- Comment #1 from Aleix Pol <aleixpol@kde.org> --- > We are not forwarding the environment variables to the Konsole tool view. I > wonder if we want that, though... > > -- > You are receiving this mail because: > You reported the bug.
Can someone set the version to 4.7.1?
If you think this helps? ;p
I hope it decreases the probability of a developer thinking the version is too old and asking to reconfirm this. :P
Bumped on kdevelop 5.2.1
Created attachment 111926 [details] Patch attempt for fixing bug. Find attached a patch trying to fix the bug. I have tested and works as *I* expect but maybe it is not the correct solution. Feel free to comment on it or propose improvements. Note: I have found an artifact when launcher profile is the default profile. In this case no profile is written in the configuration file so profile name is found to be empty and a warning is issued.
Git commit 6b7846263088b1c1ec803c445a1315dfa029f311 by Sven Brauch, on behalf of Ral Snchez Siles. Committed on 16/08/2018 at 12:18. Pushed by brauch into branch '5.3'. Inject environment profile variables into debug process environment. Summary: Extends DebugJob and DebugSession classes including launch configuration environment variables. The approach taken is getting the environment profile name within the debug process, storing it in the debug job and injecting the environment variables in the debuggee just before it is launched Reviewers: #kdevelop, brauch Reviewed By: #kdevelop, brauch Subscribers: brauch, kdevelop-devel, apol, vkorneev Tags: #kdevelop Differential Revision: https://phabricator.kde.org/D14870 M +2 -1 debugger/debugjob.cpp M +1 -0 debugger/debugjob.h M +15 -1 debugger/debugsession.cpp M +3 -1 debugger/debugsession.h M +13 -0 debugger/pdblauncher.cpp https://commits.kde.org/kdev-python/6b7846263088b1c1ec803c445a1315dfa029f311
Reopening this since it is only fixed for pdb, but not for konsole.