fix: <<EOF incompatibility on windows #448
Open
+11
−16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
EOF incompatibility on Windows refers to an issue where the 'End of File' (EOF) marker behaves differently compared to other operating systems, such as Linux or macOS. In Windows, text files often use a combination of carriage return and line feed (CRLF) as line terminators, while other systems use only a line feed (LF). This discrepancy can cause problems when sharing or processing files across different platforms, especially in programming environments, version control systems, or file parsing tasks, leading to incorrect file interpretations or unexpected behavior.