https://bugs.kde.org/show_bug.cgi?id=387259
--- Comment #3 from RJVB <rjvber...@gmail.com> --- You can already set dedicated profiles for such actions, so it's already possible to apply a different profile to KDevelop itself. Applying the default env. profile to KDevelop is trivial to do, the only thing missing is support for session-specific env. profiles -- something which is probably useful even without it being applied to KDevelop itself. Of course you can set up session-specific wrappers around KDevelop. It's just not elegant; reducing the number of job-specific scripts etc. you have to write is IMHO among the things modern development tools are designed to do. I don't see how this is more power-user than providing a built-in HTML documentation browser (which you can easily launch manually too). Not to mention the fact that KDevelop is also used on platforms where scripts aren't such an intuitive tool for everyone. -- You are receiving this mail because: You are watching all bug changes.
