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

in the vscode'terminal,I can't use the history command #10368

Closed
bitcrazed opened this issue Aug 9, 2016 · 5 comments
Closed

in the vscode'terminal,I can't use the history command #10368

bitcrazed opened this issue Aug 9, 2016 · 5 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@bitcrazed
Copy link

From @czmecho on August 9, 2016 1:35

Please use the following bug reporting template to help produce actionable and reproducible issues:

  • Your Windows build number win 10 14393.10 && vscode 1.4
    when I use the powershell or cmd ,I can use the PgUp or the PgDn keys to roll back to use the history command.
    but when I call the bash.exe ,it don't work.

    btw,can I change the background color ,I don't like the color like this.

Copied from original issue: microsoft/WSL#828

@bitcrazed
Copy link
Author

From @fpqc on August 9, 2016 15:3

Yeah, seems to be related to the same problem we've had to work around since about day 1 with ConEMU. It's another console glitch. In ConEmu you could get around it by launching bash with special arguments like -cur_console:p, but I don't know if VS code has similar arguments you can throw in to make its integrated terminal work right.

@bitcrazed
Copy link
Author

From @zadjii-msft on August 9, 2016 22:38

I would open this as a bug on the VSCode team (https://github.com/Microsoft/vscode) as this is more an issue with their built-in console, rather than an embedded conhost window

@bitcrazed
Copy link
Author

bitcrazed commented Aug 9, 2016

Moved from BashOnWindows repo.

Please be sure to notify OP (@czmecho) when investigating.

@fpqc
Copy link

fpqc commented Aug 9, 2016

@bitcrazed Probably should change the title (which made sense in the BashOnWindows repo, but will probably not be specific enough here)

@Tyriar
Copy link
Member

Tyriar commented Aug 12, 2016

Duplicate #10163

@Tyriar Tyriar closed this as completed Aug 12, 2016
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Aug 12, 2016
@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.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

3 participants