When making macros that execute osc strings, if the text wraps onto the next line (not visible until text is inserted) it adds a space in the string, making it invalid.
So far I can get around this by making the macro display larger so the text does not wrap.
Is this part of the design?
It would help to see an example of your string, but this is almost certainly caused by this bug: [EOS-32194] Editing Macros can cause the cursor to jump to a new line
Take a look at this .gif I put together:
Notice that after I enter the string, the "l" from _long_ gets stuck on the end of the string.
Does this match what you're seeing, or are you seeing something different?
That looks the same, is there a fix yet or a better work around than making the display larger?