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

Problematic ANSI escape #2285

Closed
2 tasks done
jaydenseric opened this issue Sep 25, 2017 · 2 comments
Closed
2 tasks done

Problematic ANSI escape #2285

jaydenseric opened this issue Sep 25, 2017 · 2 comments
Labels
👆 Is Upstream Issue is the fault of something Hyper uses and not Hyper itself

Comments

@jaydenseric
Copy link

jaydenseric commented Sep 25, 2017

  • I am on the latest Hyper.app version

  • I have searched the issues of this repo and believe that this is not a duplicate

  • OS version and name: MacOS Sierra v10.12.6

  • Hyper.app version: 2.0.3 (canary)

  • The issue is reproducible in vanilla Hyper.app: Is Vanilla

Issue

In a file called bug.js:

process.stdout.write('One\n')

// ANSI escape to clear the screen
// See https://github.com/sindresorhus/ansi-escapes/blob/v3.0.0/index.js#L77
process.stdout.write('\u001Bc')

process.stdout.write('Two\n')

Running node bug in Hyper outputs:

wo

When it should be:

Two

The Terminal app has the correct output (although it does not correctly clear the scroll history, but that's another story).

@Stanzilla
Copy link
Collaborator

@jaydenseric Hey there, could you test this in the Visual Studio Code terminal, please? If it happens there as well, it's xtermjs/xterm.js#1395 otherwise Hyper's fault.

@Stanzilla Stanzilla added the 👆 Is Upstream Issue is the fault of something Hyper uses and not Hyper itself label Apr 23, 2018
@LabhanshAgrawal
Copy link
Collaborator

Tested using the latest canary build
It seems to be working properly
Feel free to open a new issue if you face any other problems

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
👆 Is Upstream Issue is the fault of something Hyper uses and not Hyper itself
Projects
None yet
Development

No branches or pull requests

3 participants