-
-
Notifications
You must be signed in to change notification settings - Fork 271
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
if the text is wider than the term every frame is printed on a new line #7
Comments
Another possible solution is to support wrapped text. I'm not able to check to see if #4 is a possible solution to this issue at this time. |
I was trying out the @dylang work around, where we limit the line size to the size of the The following gif illustrates the result of such implementation, if it's something in line with what you have in mind, I can prepare a PR. |
This could probably be fixed by using |
By replacing |
* Conform with latest XO * Handle wrapped text Count how many rows are taken up by the spinner and the text and clear the appropriate number of lines. Fix clear() so it doesn't clear *further* lines until render() is called again. Fixes #38. Fixes #7. * Add hideCursor option Fixes #27. Users may still hide the cursor outside of Ora. * Test with Node.js 8 and 9 * Properly clear empty lines * Consistently set linesToClear to 0 once cleared
Problem
If the text is too long, every frame is printed on a new line, eventually filling up the screen.
Example
### Real-world example - https://github.com/dylang/npm-check/issues/98 ### Possible workaround - Limit text to `process.stdout.columns - 2` (spinner and the space next to the spinner)
The text was updated successfully, but these errors were encountered: