[Bug] Env file not protected when starting repository with env last opened

[The-LukeZ]

Steps:

1. In VSC open your env file with double click on it
2. Close VSC
3. Reopen VSC

-> Env file shown with values - "not protected"

[sametcn99]

This likely happens because VSCode restore previously open editors before extensions finish loading at startup. I am going to look into this more deeply. Thank you for reporting.

[sametcn99]

You can see that extensions are loading after the application starts by checking the activating extensions message in the bottom status bar.

[The-LukeZ]

aah, yes that is true. hm, I guess there is nothing you can do about this, other than writing a message in the extension description, can you?

[sametcn99]

I'm gonna try to fix it first, but if it's not possible, I'll add the note to the description for sure.

[The-LukeZ]

nice, thanks!