Skip to content

Use \n in vignette, not \r\n #7184

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

Merged
merged 1 commit into from
Jul 16, 2025
Merged

Use \n in vignette, not \r\n #7184

merged 1 commit into from
Jul 16, 2025

Conversation

MichaelChirico
Copy link
Member

Somewhat annoyed that GitHub didn't flag this the first time around, I suspect the parent company is to blame 🙃

My local git copy really doesn't like there being a CRLF file around.

@MichaelChirico MichaelChirico requested a review from a team as a code owner July 16, 2025 16:44
@MichaelChirico MichaelChirico merged commit 8f5ffa8 into master Jul 16, 2025
9 checks passed
@MichaelChirico MichaelChirico deleted the vignette-crlf branch July 16, 2025 16:44
Copy link

codecov bot commented Jul 16, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.77%. Comparing base (32e5aea) to head (b765957).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #7184   +/-   ##
=======================================
  Coverage   98.77%   98.77%           
=======================================
  Files          81       81           
  Lines       15203    15203           
=======================================
  Hits        15017    15017           
  Misses        186      186           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ChristianWia
Copy link
Contributor

ChristianWia commented Jul 16, 2025

I dont know from where is this problem. Reports just said that my branch was no longer aligned with the master and requested to solve the conflicts. Web interface just proposed the complete file selected in the modification - which I founded rather strange, but must go through to complete the step. Any idea ?

@MichaelChirico
Copy link
Member Author

@ChristianWia I think your IDE/editor is using CRLF (\r\n) line endings, please change the setting so that it uses LF only (\n), if you search it should be easy to find.

From within R, you can do f <- 'vignettes/...'; writeLines(readLines(f), f) to overwrite all the existing files with \r.

@ChristianWia
Copy link
Contributor

ChristianWia commented Jul 16, 2025

@ChristianWia I think your IDE/editor is using CRLF (\r\n) line endings, please change the setting so that it uses LF only (\n), if you search it should be easy to find.

From within R, you can do f <- 'vignettes/...'; writeLines(readLines(f), f) to overwrite all the existing files with \r.

As for the file corrections, I just used the web site editor proposed online by github in a standard way to solve the merge conflict (the pen icon). I have had no control on the EOL chars definition . Really strange. ....

@MichaelChirico
Copy link
Member Author

Here's my understanding:

GitHub "simple" editor is not well-suited for an end-of-line character resolution, so it's become awkward. Options I see are (1) make the edits locally instead (2) use the in-browser VScode editor https://docs.github.com/en/codespaces/the-githubdev-web-based-editor

@ChristianWia
Copy link
Contributor

so the worm was in the apple. Will try githubdev editor on next updates. very clear explaination, i like! thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants