-
Notifications
You must be signed in to change notification settings - Fork 23
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
Use uniform spacing and (LF-only) line endings #283
Comments
Thanks. I never realized this. So:
|
Fixed in branch |
Deployed a minute ago. |
@phbernard: nitpicking but manifest.json does not have the end of file line break like the browserconfig.xml has. :) |
Hex editor speaking :) Both Do you observe something else? |
Yeah. I tried it 3 times and the result is the same. The manifest doesn't
have the end of file line break while the xml does :)
…On Jan 18, 2017 20:35, "Philippe Bernard" ***@***.***> wrote:
Hex editor speaking :) Both manifest.json and browserconfig.xml have
UNIX-style (ie. 0x0A) end of line.
Do you observe something else?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#283 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAVVtTQtKktyUyjE035UPNbNzmOJ5A5Lks5rTltsgaJpZM4KOVD->
.
|
Oh, okay! The final line break at the end of the file! Sorry, I misread your first message, I thought you were talking about all ends of line. I consider this as another issue, although it would have been good to fix everything at once. I just entered #304 |
RFG uses a mix of spaces, tabs, LF, and CR+LF line separators:
The text was updated successfully, but these errors were encountered: