We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I was stung by not knowing this here.
Jokes apart, I'd be very useful if that info bar was provided. All lines end with \n?
\n
4 lines, showing 4 (POSIX-compliant file)
As before, but the last line has no line terminator?
4 lines, showing 4 (non-POSIX-compliant file)
All lines end with \r\n except the last?
\r\n
4 lines, showing 4 (typical Windows file)
Some lines end with \n other with \r\n?
4 lines, showing 4 (file with Windows and Unix mixed line endings)
All other cases?
4 lines, showing 4
Something like this I guess can be easily handled by having some function return an enum telling which case it is.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I was stung by not knowing this here.
Jokes apart, I'd be very useful if that info bar was provided. All lines end with
\n
?As before, but the last line has no line terminator?
All lines end with
\r\n
except the last?Some lines end with
\n
other with\r\n
?All other cases?
Something like this I guess can be easily handled by having some function return an enum telling which case it is.
The text was updated successfully, but these errors were encountered: