Always inherit environment when launching external terminal #1340
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was discussed on the closed issue #1317 (from this comment).
#1318 was merged in August and propagated environment to the launched external terminal, but it seemed to propagate the environment VIM was started with if and only if an environment was set somewhere in the configuration and passed to the
launch_external_terminal
function.This had the side effect, under some configuration, that the launched external terminal have an empty environment.
This pull request changed the logic when merging VIM environment and passed environment to always include the environment VIM was started with.
--
I am quite unable to determine if this could have side effects or if the fact that the parent environment not being inherited by the external terminal is working as intended, so do not hesitate to tell me if that is the case, for some reason.