Native EsyBash: 'ls' command doesn't work about esy-bash HOT 6 CLOSED

Thanks for the fix @prometheansacrifice !

Writing tests for this will be a little tricky since the cygwin binaries are already on the path when run in the test environment.

This is because we run the tests via esy b dune runtest? So the paths already get included by esy?

One alternative would be to continue using node/javascript for our tests - we could run those outside of the esy sandbox. We'd just have to change the way that we invoke esy-bash - using our executable instead of the JS script.

Another option would be that we could run the built Reason test_runner executable outside of the esy sandbox.

Or perhaps it makes sense to have two classes of tests - inline unit tests (Reason), end-to-end tests (Node runner)?

from esy-bash.

Weird. Works fine here.

c:\Users\manas\development\esy-bash\re>.\_build\default\bin\EsyBash.exe ls
_build  appveyor.yml  dune-project      esy-bash.opam  lib           package.json
_esy    bin           esy-bash.install  esy.lock.json  node_modules  tests

Infact thats how I used to make sure it was working. Nevertheless, looking into it.

from esy-bash.

Turnout it was because of cygwin on my path that didn't let me know of this issue.

from esy-bash.

Turnout it was because of cygwin on my path that didn't let me know of this issue.

Oh interesting, so it picked up the other cygwin install - thanks for the help with this @prometheansacrifice !

from esy-bash.

Writing tests for this will be a little tricky since the cygwin binaries are already on the path when run in the test environment.

from esy-bash.

Thanks for the fix, @prometheansacrifice ! Verified it works now (and we have integrated esy-bash native with master on esy! 🎉 )

from esy-bash.