2 Likes
The issue is the .env file is not .env, its .e so renaming the file would fix this issue.
Even without renaming the file. if you click again on any file after opening it, it will bring that up.
1 Like
The title’s a bit of a red herring because it looks like this has nothing to do with the .env or .e files, apparently clicking on an already open file triggers that view change, which obviously shouldn’t happen. I’ll file this for us to have a look at next week.
This also happens when renaming a file
Turns out a single missing pair of () were to blame - this should be fixed now!
1 Like