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

Terminal: split terminal fails and closes the terminal with error 259 #44270

Closed
warpdesign opened this issue Feb 23, 2018 · 5 comments
Closed

Terminal: split terminal fails and closes the terminal with error 259 #44270

warpdesign opened this issue Feb 23, 2018 · 5 comments
Assignees
@Tyriar
Labels
*not-reproducible Issue cannot be reproduced by VS Code Team member as described terminal General terminal issues that don't fall under another label windows VS Code on Windows issues

Comments

@warpdesign
Copy link
Contributor

warpdesign commented Feb 23, 2018 •
edited
Loading

Steps to Reproduce:

  1. open the integrated terminal
  2. type bash to enter wsl
  3. use nano to open any text file
  4. type ctrl + shift + p and use the split terminal function

Result: the bash terminal with nano is closed and this error appear in VSCode:

image

I'm on Windows 10 Insiders (x64), and that's with VSCode Insiders:

Version 1.21.0-insider
Commit ce13bb0
Date 2018-02-23T05:19:18.064Z
Shell 1.7.9
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64
@vscodebot
Copy link

vscodebot bot commented Feb 23, 2018

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@vscodebot vscodebot bot added the terminal General terminal issues that don't fall under another label label Feb 23, 2018
@warpdesign warpdesign changed the title Terminal: split closes the terminal with an error Terminal: split closes the terminal with an error 259 Feb 23, 2018
@warpdesign warpdesign changed the title Terminal: split closes the terminal with an error 259 Terminal: split terminal fails and closes the terminal with error 259 Feb 23, 2018
@Tyriar Tyriar added the windows VS Code on Windows issues label Feb 23, 2018
@Tyriar Tyriar added this to the February 2018 milestone Feb 23, 2018
@Tyriar
Copy link
Member

Tyriar commented Feb 26, 2018

I can't seem to repro. I can get nano's state to mess up which is kind of expected when resizing (this #26375). I can't get it to crash though. I wasn't testing on Windows Insiders though, maybe that's something to do with it?

@Tyriar Tyriar removed this from the February 2018 milestone Feb 26, 2018
@felipebraga
Copy link

The item on context menu in the terminal integrated Split is in the worst place ever.

@Tyriar
Copy link
Member

Tyriar commented Mar 9, 2018

@felipebraga I dunno about work place ever, this is pretty bad:

screen shot 2018-03-09 at 7 02 00 am

But yes I think I'll move it just under New Terminal 😄 #45410

@Tyriar Tyriar added the *not-reproducible Issue cannot be reproduced by VS Code Team member as described label Mar 9, 2018
@vscodebot
Copy link

vscodebot bot commented Mar 9, 2018

We closed this issue because we are unable to reproduce the problem with the steps you describe. Chances are we've already fixed your problem in a recent version of VS Code. If not, please ask us to reopen the issue and provide us with more detail. Our issue reporting guidelines might help you with that.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Mar 9, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Apr 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Tyriar Tyriar

Labels
*not-reproducible Issue cannot be reproduced by VS Code Team member as described terminal General terminal issues that don't fall under another label windows VS Code on Windows issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@warpdesign @Tyriar @felipebraga