Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

demarcation strings could collide with regular output #2

Open
darrenderidder opened this issue Jul 20, 2011 · 2 comments
Open

demarcation strings could collide with regular output #2

darrenderidder opened this issue Jul 20, 2011 · 2 comments

Comments

@darrenderidder
Copy link
Collaborator

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.

@mk-pmb
Copy link
Contributor

mk-pmb commented Apr 6, 2014

Would MIME-style boundaries solve it?

@darrenderidder
Copy link
Collaborator Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants