View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002368 | Double Commander | Default | public | 2019-09-28 03:05 | 2019-10-06 15:32 |
| Reporter | arun | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | duplicate | ||
| Projection | none | ETA | none | ||
| Platform | Windows | OS | Windows | OS Version | 10 |
| Product Version | 0.9.6 | Product Build | 2019/09/01 | ||
| Summary | 0002368: When opening terminal from DoubleCommander, it doesn't inherit latest environment variable changes | ||||
| Description | 1. Open double commander and navigate to some folder. 2. open cmd.exe from double commander itself, it will bring up cmd window. 3. echo %some_existing_variable% in the cmd.exe. It will print the current value. 4. Close the cmd.exe window. 5. Open environment variable editor and edit the existing env variable or add a new one and close the env editor. 6. Via double commander, open cmd.exe 7. echo the variable that was modified previously. 8. It will still display the old value and not the new updated value. 9. If you repeat the same steps above with Windows explorer, it will inherit the new value after the env variable is updated. | ||||
| Tags | No tags attached. | ||||
| Fixed in Revision | |||||
| Operating system | Windows | ||||
| Widgetset | |||||
| Architecture | 64-bit | ||||
| duplicate of | 0001611 | acknowledged | Terminal don't apply new system environment variable |
