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
$ 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
The text was updated successfully, but these errors were encountered:
chexxor
changed the title
psc-package sources hard to use on windowspsc-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
$ purs compile -o output $(psc-package sources) 'src/**/*.purs'
will fail becausepsc-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...
The text was updated successfully, but these errors were encountered: