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
A curl utility problem that strongly effects my work with Bash on Windows #2939
Comments
@therealkenc I can't test at the moment but I assume you meant to pipe it through |
Sure, if you want to be all fancy about it. |
I now saw that dos2unix isn't native in Ubuntu. Crap. I than have execute
|
Or you could reupload your script atfter running dos2unix on it. |
|
AFAIK if I run the Thanks anyway, |
This is not a WSL problem per se, but deals heavily with Bash in Windows (Linux users seem not to encounter this). It roams my work with WSL and avoids me from working with
curl
smoothly:I have this [remote Bash script][1] In GitHub that I already executed successfully line by line, several times (in different versions).
As it is quite frustrating to copy paste all lines each test, I tried to execute the remote Bash script by its raw form with
curl
, but it fails in various tries:or
Both failed totally after about 3 seconds with the error:
I theorized I might need to translate out all carriage returns, hence tried:
This brought partial execution of the script. For example, while
apt-get install
,export
,git clone
,rm -rf ${repo}/.git/
, and a few other operations went fine, thewget
/unzip
and processing of a few files with leading tabs failed to be processed correctly.I thought it might be that GitHub GUI changes leading whitespaces from tab to space and vice versa, in some sections in the code, so I tried to change all leading whitespaces into tabulations:
The result was seemingly identical to the previous one.
Due these 4 ways fail, I wonder what else is available. Sadly I've yet to find other examples in Google.
The text was updated successfully, but these errors were encountered: