-
CommentStreams:D477d4e3c99c1db004219c2abe6b60fa: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<div> | <div>Thank you for your feedback.</div><div>We actually discovered and fixed this issue a long time ago. You can directly download the latest repository code from https://github.com/geekworm-com/xscript. After extracting the files, you can check the <code>.sh</code> files to see if there are any <code>0x0D</code> (<code>\r</code>) characters.</div><div>If the scripts you downloaded still contain <code>0x0D</code> characters, it is highly likely related to your local Git configuration. Specifically, if your Git is set to <code>core.autocrlf=true</code> (which is the default on Windows), Git will automatically convert Unix line endings (LF) to Windows line endings (CRLF, <code>0x0D 0x0A</code>) when checking out the files. This extra <code>0x0D</code> </div> | ||
Latest revision as of 18:59, 26 June 2026
Thank you for your feedback.
We actually discovered and fixed this issue a long time ago. You can directly download the latest repository code from https://github.com/geekworm-com/xscript. After extracting the files, you can check the
.sh files to see if there are any 0x0D (\r) characters.If the scripts you downloaded still contain
0x0D characters, it is highly likely related to your local Git configuration. Specifically, if your Git is set to core.autocrlf=true (which is the default on Windows), Git will automatically convert Unix line endings (LF) to Windows line endings (CRLF, 0x0D 0x0A) when checking out the files. This extra 0x0D