Open letmaik opened 6 years ago
PowerShell on Windows 10 machines should be using PSReadline, so this would be why the command history is intact. CMD itself doesn't have command history and I believe this is usually provided by the doskey app in the same directory as $ComSpec, usually C:\Windows\System32.
I have the issue with up arrow key in cmd shortcut, too But if I open cmd via Win+R, the colors are not solarized. Do you have any clue?
I had the same issue and fixed it by setting "buffer size" and "number of buffers" to 10 in the command prompt properties. You then need to re-open the command prompt window.
After applying the dark color scheme (including the registry update) when I open cmd and enter a command, then press the up arrow key, I only get a blank line and not the last command. If I open cmd via Win+R everything is working as it should, and the colors are still solarized (I guess for that case it uses the registry settings and not the updated shortcut .lnk). I reproduced this on two Windows 10 machines. EDIT: On PowerShell this problem does not appear.