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
ESCape "\n" codes #3246
ESCape "\n" codes #3246
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change looks fine, but please make your commit message follow our standard style. Perhaps:
CURLINFO_OS_ERRNO.3: escape "\n" codes
Too late to edit the commit message now. Only the title is editable. At least here on Github. |
You can always edit the commits in your branch ( |
@gvanem |
@kdudka I know that. But it's a big hassle for me to |
Groff / Troff will display a: printaf("Errno: %ld\n", error); as: printf("Errno: %ld0, error); when a "\n" is not escaped. Use "\\n" instead. Closes #3246
1193789
to
073332b
Compare
I disagree with that, but perhaps the biggest change and improvement compared to the "old days" and now is that we run a bazillion tests on the change before we merge it... I squashed and forced-pushed these commits with a new commit message! |
In a
.nf
section, Groff / Troff will display a:as:
when a
"\n"
is not escaped. Use"\\n"
instead.