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
{{ message }}
Repository navigation
demarcation strings could collide with regular output #2
Since the stderr >>> prompt didn't work very well to demarcate command responses, I added a header and footer to the command response, which are just "COMMAND START" and "COMMAND END". Which is pretty lame because these strings could appear somewhere in the normal output. Making them more unique and making the regex test that looks for them a little more explicit would be better.
Something like that. The solution I had in mind is just to use a random string instead of a hard-coded one; I briefly looked into generating UUID's, but now consider that to be overkill.
Activity
mk-pmb commentedon Apr 6, 2014
Would MIME-style boundaries solve it?
darrenderidder commentedon Apr 6, 2014
Something like that. The solution I had in mind is just to use a random string instead of a hard-coded one; I briefly looked into generating UUID's, but now consider that to be overkill.