Skip to content

Redirect process output directly to screen instead of waiting for line endings? #196

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

Closed
seaneagan opened this issue Apr 21, 2015 · 1 comment
Labels

Comments

@seaneagan
Copy link
Contributor

Currently runAsync buffers the output until encountering a line ending, and then passes it to log. log currently just forwards to print, but we will likely want to change that in the future. Some potential changes:

However, some apps use ansi escape sequences to do clever UI enhancements, such as a progress animation, or not actually printing out newlines, but rather replacing the line output once a new line occurs, such as test (see #194). But when grinder calls these processes they will likely eventually (https://dartbug.com/21821) see the stdioType as a pipe, and disable these features anyways. Unless dart will provide some way for a child process to inherit the stdio (stdioType especially) of a parent process (grinder in this case)?

So should runAsync (and it's callers) have a mode which enables these interactive features, and doesn't buffer the output for later consumption by log? Should it be the default?

@devoncarew
Copy link
Contributor

dupe of #290

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

No branches or pull requests

2 participants