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

lix help is unclear for some commands #184

Open
NQNStudios opened this issue Apr 29, 2023 · 1 comment
Open

lix help is unclear for some commands #184

NQNStudios opened this issue Apr 29, 2023 · 1 comment

Comments

@NQNStudios
Copy link
Contributor

 Supported commands:

    install <url> [as <lib[#ver]>] : install lib from specified url
    install haxe <version>|<alias> : install specified haxe version
        use haxe <version>|<alias> : use specified haxe version
                  dev <lib> <path> : use dev version of library
   download haxe <version>|<alias> : download specified haxe version
             scope [create|delete] : creates or deletes the current scope or
                                     inspects it if no argument is supplied
                     haxe-versions : lists currently downloaded versions
      download [<url[#lib[#ver]]>] : download lib from url if specified,
                                     otherwise download missing libs
                   run lib ...args : run a library
                    --version / -v : print version
          run-haxelib path ...args : invoke a haxelib at a given path following haxelib's conventions

The convention seems to be <name> for arguments, but this is not followed for run lib ...args and run-haxelib path ...args. Also, run-haxelib must take a lib argument too, so does it go before or after the path?

@NQNStudios
Copy link
Contributor Author

Am I misunderstanding run-haxelib's explanation? I thought it meant that the path argument will be used as the cwd for the program, but if it's actually the path to a haxelib folder stored locally, then it makes sense that there's no lib argument.

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

1 participant