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

psc-package sources command hard to use on windows #103

Open
chexxor opened this issue Apr 19, 2018 · 0 comments
Open

psc-package sources command hard to use on windows #103

chexxor opened this issue Apr 19, 2018 · 0 comments

Comments

@chexxor
Copy link

chexxor commented Apr 19, 2018

$ purs compile -o output $(psc-package sources) 'src/**/*.purs' will fail because psc-package sources outputs "" directory separator on windows, but my bash shell (mingw) only supports "/" dir separator.
Also, I can't do subcommands like $(...) on a normal windows shell.

I'd guess psc-package is using a library which sees the host OS is windows so outputs in windows format, but psc-package can't use it because it doesn't parse it into a canonical cross-platform file path format.

One suggestion was to pipe it to sed before sending it to purs, but...

$ purs compile -o output $(psc-package sources | sed 's#\\#/#g') 'src/**/*.purs'
bash: /c/Users/chexxor/bin/purescript-0.11.7/purs: Argument list too long
@chexxor chexxor changed the title psc-package sources hard to use on windows psc-package sources command hard to use on windows Apr 19, 2018
Rembane pushed a commit to Rembane/psc-package that referenced this issue May 26, 2018
* add node-postgres

* update node-postgres version to v3.0.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants