-
Notifications
You must be signed in to change notification settings - Fork 422
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
Generated docs: git chokes on mixed line endings #1965
Comments
I did a manual
I thought that the above line would prevent this issue... No idea what is going on. Hopefully this manual action will allow you to make progress. |
Yes, this is helpful, thanks a lot. I just realized that inside the directories |
@deining Sorry for the delay... |
@deining Are we okay to close this ticket, or is there any more work remaining? (Happy to do more, just let me know...) |
How to reproduce:
I'm on a linux box. Immediately after cloning the repo, I do see modified files:
git config --get core.autocrlf
doesn't print out anythig, so I think the default value offalse
applies.I do have an idea what is causing this behavior: the generated html files do have mixed line endings.
For e.g.
docs/man/index.html/
has these mixed line endings (on a Linux checkout):Line 1-1711: LF
Line 1712-1786: CR/LF
Line 1787-19079: LF
AFAICS, The CR/LF in line 1712 - 1786 are introduced by the gradle asciidoctorj-tabbed-code-extension that is used from the gradle
asciidoc
task.picocli/gradle/docs.gradle
Lines 2 to 10 in cc0602b
These are the two files that included as inline
.css
and.js
into the generated html documents:https:/bmuschko/asciidoctorj-tabbed-code-extension/blob/master/src/main/resources/codeBlockSwitch.css
https:/bmuschko/asciidoctorj-tabbed-code-extension/blob/master/src/main/resources/codeBlockSwitch.js
As far as I can see, these files are not part of the picocli repo, but are included during gradle run.
So far my investigations, I hope I'm correct with my analysis. I'm not sure about the best solution for this. My first thought was an additional build step that normalizes the line endings of the generated html files. Maybe there is a more elegant solution that I can't see right now?
I would like to see this resolved. This is an issue that bothers me for quite some time now. With this obstacle removed, it is more likely you will see further commits from me in the future 😄 .
The text was updated successfully, but these errors were encountered: