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

How to replace SetConsoleHistoryInfo in a modern ConPTY world? #242

Open
jrobbins-LiveData opened this issue Jan 18, 2022 · 0 comments
Open

Comments

@jrobbins-LiveData
Copy link

I've read that SetConsoleHistoryInfo is deprecated, but I don't understand how to add command history capabilities to a shell I create with cmd /k without this API. I've searched the issues (e.g. microsoft/terminal#2558) and am unclear what this means for using cmd.exe. The doc says

Tip

This API is not recommended and does not have a virtual terminal equivalent. This decision intentionally aligns the Windows platform with other operating systems where the individual client application acting as a shell or interpreter is expected to maintain its own user-convenience functionality like line reading and manipulation behavior including aliases and command history. Applications remoting via cross-platform utilities and transports like SSH may not work as expected if using this API.

Will cmd.exe get rewritten to support ConPTY, and gain a new, "application-specific" way of configuring command history buffer count?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant