# go: Write \`envFile\` properties back to \`env\` config \(\#34300\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/fbead09c30ca1b1371ae485958fc685f1bcf2d59)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: fbead09c30ca1b1371ae485958fc685f1bcf2d59

Requested commit: fbead09c30ca1b1371ae485958fc685f1bcf2d59

Commit: fbead09c30ca1b1371ae485958fc685f1bcf2d59

Tree: d42636cec9e6cdaeb8171c3479761b0b36ccedf8

Author: Lukas Spiss

Committer: GitHub

## Message

```
go: Write `envFile` properties back to `env` config (#34300)

Closes https://github.com/zed-industries/zed/issues/32984

Note that while https://github.com/zed-industries/zed/pull/33666 did the
reading of the `envFile` just fine, the read values were never passed
along. This was mentioned by [this
comment](https://github.com/zed-industries/zed/pull/33666#issuecomment-3060785970)
and also confirmed by myself.

With the changes here, I successfully debugged a project of mine and all
the environment variables from my `.env` were present.

Release Notes:

- Fix Go debugger ignoring env vars from the envFile setting.
```

## Parents

- [0797f7b66e4187a599b88532545da46071f854f4](https://git.cafe/gitcafe/zed/commit/0797f7b66e4187a599b88532545da46071f854f4?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/fbead09c30ca1b1371ae485958fc685f1bcf2d59?format=markdown)