Repository navigation
Use UTF-8 encoding in all files - #215
Merged
Merged
Conversation
charjr
force-pushed
the
utf8-encoding
branch
2 times, most recently
from
July 15, 2026 18:18
e9d3594 to
f14ae6f
Compare
The purpose of this set of commits is to use utf-8 encoding. So I do not want to overstep the scope. Also indent size does not play nicely with elisp indentation, which has a lot of contextually different indentation levels: i.e. `let' and `if' statements.
Collaborator
|
Please let me know when this is ready to merge, the change is looking good to me. |
Contributor
Author
@NathanLovato I believe it is ready to go now. 🚀 Thank you for reviewing! 💯 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Important
Ignore whitespace changes to review this PR
What Changed?
6 files used MS-DOS encoding, which (depending on how you use git) leads to seeing strange
^Ms at the end of every single line.This PR adjusts these files to use UTF-8 encoding for consistency with the rest of the package.
As such, the PR looks huge because it changes every single end-of-line character. But if you ignore whitespace (see the screenshot at the top) then the only real change is to add a
.editorconfigfile to reduce the risk of this happening again.Closes #139