You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
I've read that
SetConsoleHistoryInfo
is deprecated, but I don't understand how to add command history capabilities to a shell I create withcmd /k
without this API. I've searched the issues (e.g. microsoft/terminal#2558) and am unclear what this means for usingcmd.exe
. The doc saysWill
cmd.exe
get rewritten to support ConPTY, and gain a new, "application-specific" way of configuring command history buffer count?The text was updated successfully, but these errors were encountered: