-
Notifications
You must be signed in to change notification settings - Fork 11
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
Windows carriage return pollution #215
Comments
Another spooky oddity, from a Unix system, the following for i in {1..1981}; do echo ""; done > newlines.metta
unix2dos newlines.metta
mettalog newlines.metta triggers a never ending stream of errors, such as
If the number of lines is less (say 1980 instead of 1981) then the errors disappear. Likewise if the file is not converted to DOS format. Spooky, isn't? |
Aha thank you.. that is werid about the odd/even stuff OK i am thinking about dos2unix-ing everyting anyways.. get ready for masive changes |
Wild i had to add some newlines in VIM at the bottem of in order for dos2unix to work on that file.. ~/metta-wam$ git commit -am "Yet another attempt to dos2unix everything" |
ngeiswei this could have been my fault - I use a windows-based IDE. Did you find those stray \r's in any other file? I didn't commit anything to metta_envvars.sh. My last commit was in metta_repl.pl. Can you check whether that one has \r's for you please? |
Windows carriage return characters (
^M
in Unix) sometimes find their way in the code. The latest targeted file for me wasscripts/envvars_mettalog.sh
which crashed the installation of MeTTaLog with errorIt's a not a big deal, I just apply
dos2unix
on the file to fix the problem, but I thought I would mention it nonetheless.Also, I tried to create a PR with the fixed file but weirdly enough git does not seem to register the change.
The text was updated successfully, but these errors were encountered: