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.

Sign up for GitHub

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

Jump to bottom

The cursor can't move in the Ruby irb Mode in the Integrated Terminal #14577

Closed
satoukick opened this issue Oct 27, 2016 · 5 comments
Closed

The cursor can't move in the Ruby irb Mode in the Integrated Terminal #14577

satoukick opened this issue Oct 27, 2016 · 5 comments
Assignees
@Tyriar
Labels
bug Issue identified by VS Code Team member as probable bug terminal General terminal issues that don't fall under another label upstream Issue identified as 'upstream' component related (exists outside of VS Code) windows VS Code on Windows issues

Comments

@satoukick
Copy link

  • VSCode Version: Code 1.6.1 (9e4e44c, 2016-10-13T16:21:53.542Z)
  • OS Version: Windows_NT ia32 10.0.14393
  • Extensions: austin.code-gnu-global-0.2.1, ms-vscode.cpptools-0.9.2

Ruby version is 2.2.5

In the Integrated Terminal,The cursor can move in the normal terminal , but can't when entered the irb!

default

PS:It actually works when calling irb on the normal cmd.exe
@Tyriar Tyriar added bug Issue identified by VS Code Team member as probable bug terminal General terminal issues that don't fall under another label windows VS Code on Windows issues upstream Issue identified as 'upstream' component related (exists outside of VS Code) labels Oct 27, 2016
@Tyriar Tyriar mentioned this issue Oct 27, 2016
Closed
@Tyriar
Copy link
Member

Tyriar commented Oct 27, 2016

Duplicate #14613

@Tyriar Tyriar closed this as completed Oct 27, 2016
@Tyriar Tyriar added *duplicate Issue identified as a duplicate of another issue(s) and removed bug Issue identified by VS Code Team member as probable bug labels Oct 27, 2016
@Tyriar
Copy link
Member

Tyriar commented Jan 16, 2017

This should hopefully be fixed in tomorrow's Insiders build (via 63f1fa6). Please let me know if it still reproduces.

See #13625 for more information.

@Tyriar
Copy link
Member

Tyriar commented Jan 27, 2017

#13625 does not fix this issue

@Tyriar Tyriar reopened this Jan 27, 2017
@Tyriar Tyriar added bug Issue identified by VS Code Team member as probable bug and removed *duplicate Issue identified as a duplicate of another issue(s) labels Jan 27, 2017
@Tyriar Tyriar mentioned this issue Jan 27, 2017
Closed
@Tyriar
Copy link
Member

Tyriar commented Jan 27, 2017

Upstream issue rprichard/winpty#99

@satoukick satoukick reopened this Feb 27, 2017
@satoukick
Copy link
Author

Thanks. I will check out.

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Tyriar Tyriar

Labels
bug Issue identified by VS Code Team member as probable bug terminal General terminal issues that don't fall under another label upstream Issue identified as 'upstream' component related (exists outside of VS Code) windows VS Code on Windows issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Tyriar @satoukick