You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Perhaps a better solution is to reload the current environment each time a folder is opened (either at LiteIDE startup or during a LiteIDE session). With some extra smarts in the env file parser, it would then be possible to include project directory information in the standard env file e.g. in order to customise GOPATH.
I currently use the environment "switcher" to change between go and gopherjs builder (not perfect, but it works: https://github.com/bep/go-or-gopherjs)
It would be great if I would somehow load environments automatic per project / package.
Currently, LiteIde allows a file or folder to be included as a command-line option.
i.e. liteide.exe myproject
will start up LiteIde at the specified project directory.
This is very convenient when LiteIde is invoked from a batch file (or script) within a custom project environment.
It would be even more convenient if I could also set the active LiteIde environment via the command-line using, say, an "-e" option
e.g. liteide.exe -e custom.env myproject
The text was updated successfully, but these errors were encountered: