You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Empty line appears after 3rd rem, and another rem appears after it (which wasn't present in the original nor is required for line wrapping)
Stray m appears after the extraneous rem (the first point)
The long xxxx... line is put on a separate line rather than being left alone on its own rem-prefixed line (since xxxx... cannot be broken and wrapped)
Last two lines are just all wrong: one starts with em em rather than rem, then goes an empty rem line and the rest of it goes on the separate line without the rem prefix
The last line in the output has stray em near the end
Expected output:
rem foo foo ...
rem foo foo ...
rem foo foo ...
rem
rem xxxx...
rem
rem foo foo...
rem foo foo...
rem foo foo...
Note: the purpose of rem foo (last input line) is to confirm that it's correctly joined with the preceding line - something that doesn't happen with this simple document ([ ] = selection):
[rem foo
rem foo]
I suspect there's some buffer overrun due to the comment prefix being 4 characters in this scheme since I don't see this problem with JavaScript or INI. Do we have some hardcoded limit on the prefix length?
Update: actually, one of these problems does appear in other schemes (JS/INI):
#320 enabled, F12 -> Batch File, paste this document, Ctrl+A, Ctrl+I:
Issues:
rem
, and anotherrem
appears after it (which wasn't present in the original nor is required for line wrapping)m
appears after the extraneousrem
(the first point)xxxx...
line is put on a separate line rather than being left alone on its ownrem
-prefixed line (sincexxxx...
cannot be broken and wrapped)em em
rather thanrem
, then goes an emptyrem
line and the rest of it goes on the separate line without therem
prefixem
near the endExpected output:
Note: the purpose of
rem foo
(last input line) is to confirm that it's correctly joined with the preceding line - something that doesn't happen with this simple document ([ ]
= selection):I suspect there's some buffer overrun due to the comment prefix being 4 characters in this scheme since I don't see this problem with JavaScript or INI. Do we have some hardcoded limit on the prefix length?
Update: actually, one of these problems does appear in other schemes (JS/INI):
The output must be the same but it gets an empty
;
line before the long line.The text was updated successfully, but these errors were encountered: