Bug 458041 - Setting evironment variable to empty should unset the env
Summary: Setting evironment variable to empty should unset the env
Status: REPORTED
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 5.9.220800
Platform: Snap Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-18 18:26 UTC by Ian H
Modified: 2022-08-18 18:26 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ian H 2022-08-18 18:26:41 UTC
SUMMARY
***
If there is an environment variable set that must be completely unset in order for your app to function, there is no way to unset it through the ui environment  variables. Currently setting the variable to empty does nothing (kdevelop ignores it and leaves the env alone)
Setting the variable to empty (or <unset> /something) should do a unsetenv instead of being ignored.
***


STEPS TO REPRODUCE
1. Set random env to a value prior to launching kdevelop (so that it is in the kdev environment)
2. Set that same env to an empty on the value side in launch configuration
3. print the env from your program

OBSERVED RESULT
the env variable is the same as it originally was, and is not unset (nor even set to empty string)

EXPECTED RESULT
Should be set to undefined as though you had called unsetenv

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 22.04.1