Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Command line option to set ENV #40

Closed
rvjcallanan opened this issue Jan 25, 2013 · 3 comments
Closed

Feature Request: Command line option to set ENV #40

rvjcallanan opened this issue Jan 25, 2013 · 3 comments

Comments

@rvjcallanan
Copy link

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

@rvjcallanan
Copy link
Author

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.

@bep
Copy link

bep commented Feb 22, 2017

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.

@visualfc
Copy link
Owner

please download latest version

liteide --select-env [system|win32|cross-linux64|...]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants