Scripts won't execute under Windows (cygwin) if autocrlf=true
UncleCJ opened this issue · 4 comments
UncleCJ commented
I just wanted to drop a note that I adore this set of exercises, simple enough with nice web interaction, but with a proper git repository to use in your development environment, brilliant!
A little more startup help would be useful though - it's not immediately obvious how start and verify aliases work, and since I hadn't figured out autocrlf configuration, the scripts wouldn't execute. Maybe add some hints about such things?
Best regards
CJ
fracz commented
I'm glad you like the exercises!
I am working on Windows with autocrlf=true
in Git Bash and did not face the problem you describe.
If I uderstand correctly, you had to set autocrlf=false
in order to use the aliases?
UncleCJ commented
Yes, they are excellent. I figured though since they depend on the scripts,
clarify that they are to be run in git bash and not some other shell.
Yes, that (or rather, autocrlf=input) was what got it working for me in
Cygwin. But now I'm seeing filemode mismatch between Git Bash and Cygwin
too so clearly they are my configuration issues - I'm discussing them in
#git on freenode IRC BTW.
Thank you
CJ
…On 19 January 2017 at 16:39, Wojciech Frącz ***@***.***> wrote:
I'm glad you like the exercises!
I am working on Windows with autocrlf=true in Git Bash and did not face
the problem you describe.
If I uderstand correctly, you had to set autocrlf=false in order to use
the aliases?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAD9zQWlhg36bDi7X3rpGcYAaVWEgCP1ks5rT4OngaJpZM4LoIxF>
.
--
Carl-Johan Sveningsson cj.sveningsson@gmail.com +46 734 481314
My nerdy blog - http://unclecj.blogspot.com
My micro-life - http://twitter.com/unclecj
My social life - http://facebook.com/unclecj
My professional page - http://www.linkedin.com/in/carljohan
fracz commented
Can I assume that your issue has been solved?
UncleCJ commented
Sorry, no, but I'm not working on them for the time being either. Close the
issue if you feel it is appropriate. And thanks again :-)
/CJ
…On 8 March 2017 at 21:30, Wojciech Frącz ***@***.***> wrote:
Can I assume that your issue has been solved?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAD9zeUntdEOT2TqhVYS_U7Cct015UUsks5rjw_-gaJpZM4LoIxF>
.
--
Carl-Johan Sveningsson cj.sveningsson@gmail.com +46 734 481314
My nerdy blog - http://unclecj.blogspot.com
My micro-life - http://twitter.com/unclecj
My social life - http://facebook.com/unclecj
My professional page - http://www.linkedin.com/in/carljohan