-
Notifications
You must be signed in to change notification settings - Fork 83
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix explicit line breaks in comments.
Given the bugs in the (quite ancient) C code, I wonder whether this ever worked correctly even in classic pd-l2ork. But it was definitely broken in Purr Data. The changes required to fix it are both in the C code and on the GUI / JavaScript side. Note that the implementation still uses \v (a.k.a. vertical tab a.k.a. ^K a.k.a. ASCII code 11) as a substitute for the \n newline character (which the Pd binbuf eats for breakfast, as it is just whitespace, whereas it leaves \v alone). These "fake" newline characters will only ever occur in comments when using explicit line breaks. They *will* end up in the patch file; you can verify this by looking at the .pd file in any decent text editor capable of displaying control characters. Vanilla Pd doesn't know how to handle those \v characters, so depending on its canvas font it will render them as funny-looking glyphs instead. Thus you better avoid explicit line breaks if you want to keep your patches "vanilla-clean".
- Loading branch information
Showing
5 changed files
with
46 additions
and
52 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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