Did they use sane or Windows-style newlines? Windows-style line endings are not supported everywhere.
Edit:
Variable-width handwriting is no longer considered a best practice and has been deprecated for some time. If the program did not compile with sane line endings, try rewriting the program in monospace, as support for legacy handwriting styles may have been dropped from non-LTS compiler releases.
Many editors can read config files from a file in the repository itself. And oftentimes it has the highest priority. Just gotta know the IDE of your target and they have to click “trust this project”.
See the problem with this is that even if I write code with this font, I can’t force people to read it in this font.
Of course you can. Instead of committing the code to a repository, you just take screenshots of the everything and commit that instead.
Settle down Satan.
And then you program a runtime that calls an AI to parse images and execute your code in real-time!
Related: https://stackoverflow.com/questions/5508110/why-is-this-program-erroneously-rejected-by-three-c-compilers
Did they use sane or Windows-style newlines? Windows-style line endings are not supported everywhere.
Edit:
Variable-width handwriting is no longer considered a best practice and has been deprecated for some time. If the program did not compile with sane line endings, try rewriting the program in monospace, as support for legacy handwriting styles may have been dropped from non-LTS compiler releases.
You can if you paste it into a write protected pdf
The only real way to write protect it is by printing the pdf into pdf (making it a pdf of an image).
I wonder if this font would screw up ocr?
Unless the OCR were made for this font, probably yes.
Yes. The “problem”.
Many editors can read config files from a file in the repository itself. And oftentimes it has the highest priority. Just gotta know the IDE of your target and they have to click “trust this project”.
Just add it for VSCode and Jetbrains and you cover like 75-95% of devs