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

Integrated Cmder terminal does not save command history #59230

Closed
ghost opened this issue Sep 24, 2018 · 3 comments
Closed

Integrated Cmder terminal does not save command history #59230

ghost opened this issue Sep 24, 2018 · 3 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) terminal Integrated terminal issues

Comments

@ghost
Copy link

ghost commented Sep 24, 2018

  • VSCode Version: 1.27.2 Portable
  • OS Version: Windows 10 1803

Steps to Reproduce:

  1. Cmder is integrated in VS Code by doing steps proposed here
    "terminal.external.windowsExec": "cmder",
    "terminal.integrated.shell.windows": "C:\\WINDOWS\\System32\\cmd.exe",
    "terminal.integrated.shellArgs.windows": [
        "/K",
        "%CMDER_ROOT%\\vscode.bat"
    ],
  1. Start cmder externally with cmder.exe. Execute echo test. Now the command is still listed as first entry in command history when (re)starting a) cmder.exe b) VS Code integrated Cmder and pressing up arrow.
  2. In VS Code integrated Cmder execute command echo test2. The command will be in the history of current opened shell. But when I open a) Cmder externally or b) close and restart the integrated terminal afterwards, the command does not appear there and gone completely.

Does anyone experience similar issues out there? What could be a solution to persist command history across cmder usage as external and integrated terminal?

Greetings

@vscodebot
Copy link

vscodebot bot commented Sep 24, 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 Integrated terminal issues label Sep 24, 2018
@Tyriar
Copy link
Member

Tyriar commented Sep 24, 2018

#43557

@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Sep 24, 2018
@vscodebot
Copy link

vscodebot bot commented Sep 24, 2018

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Sep 24, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 8, 2018
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) terminal Integrated terminal issues
Projects
None yet
Development

No branches or pull requests

1 participant