-
Notifications
You must be signed in to change notification settings - Fork 75
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
File with BOM and not UTF-8 ? #155
Comments
mika
added a commit
that referenced
this issue
Jan 26, 2024
The file isn't properly encoded and claims to be latin1. Convert to UTF8 to avoid broken characters in getanchors(). Thanks: flobee for the bug report Closes: #155
I like #156 ;-) just saw your sys-admin presentation at media.ccc from '23. you'are talking very fast ... watched at 75% of speed :-D |
@flobee excellent, merged now! :) Haha 8-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See my hints:
flobee@a9e10c8
downloaded zshrc files from https://grml.org/zsh/ this way:
Edit in kate and kate says: BOM exists and Line 335 (#getanchors) look damaged.
But the browser tell also weired chars.: https://github.dev/grml/grml-etc-core/blob/master/etc/skel/.zshrc#L335C40-L335C47
The text was updated successfully, but these errors were encountered: