| Summary: | environment is not inherited in new konsoles | ||
|---|---|---|---|
| Product: | [Applications] konsole | Reporter: | Gaël de Chalendar (aka Kleag) <kleagg> |
| Component: | general | Assignee: | Konsole Developer <konsole-devel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
This is a side-effect of Konsole being a single-process application in KDE 4. If you start Konsole from within an existing Konsole window then a stub-process starts, contacts the existing konsole process, asks it to create a new window and then exits. Bug #156365 is caused by the same problem. Fixed by SVN commit r795982 Yes, new konsole windows inherit thei env from their parent, now. Thanks. But when creating a new console in a new tab, the environment should be the one of the previous tab and not the one of the parent process, too. For that, should I open a new bug/wish or should this one be reopened ? > the environment should be the one of the previous tab
That is not easily possible I'm afraid. The shell stores the current environment and does not expose this information in a generic fashion to the outside world.
If the environment is important then I suggest looking into writing scripts to load and save the environment from within the shell.
|
Version: 2.0 (using KDE 4.00.80 (KDE 4.0.80 >= 20080104), compiled sources) Compiler: gcc OS: Linux (i686) release 2.6.22.12-desktop586-1mdv When launching a konsole from another one (r758617), the environment is not inherited. For example if you do > export A=a > konsole & the the env var A is not defined in the new console. This is maybe related to #154710 where the working directory is not used. But the probability is low is I don't suppose that konqueror modifies its $PWD env var ?