On Thu Apr 17 15:19:52 2025 +0000, Joe Souza wrote:
Thanks for the feedback. It wasn't clear to me how CONSOLE_READCONSOLE_CONTROL worked but now that I have looked at the docs for it, I see. Regarding the second point, this code already does what you seem to claim it does not. It supports tab-completion at any point in the command line. For example, if the user enters 'not' at C:\windows and then pressed the tab key, it is tab-completed to 'notepad.exe'. It also cycles through files and directories if the tab key is pressed at an empty command line. If this work is conflicting with other work that is ongoing, I can withdraw the request. Or, I can look into using CONSOLE_READCONSOLE_CONTROL as you suggest. I see how using that would support obtaining command line history, but I don't see how that would allow insertion of the new entered command into console's history if ReadConsole returns early due to tab key being pressed.
It's also not clear to me how the user would continue editing the command line if ReadConsole were to return early (if tab pressed) when using CONSOLE_READCONSOLE_CONTROL.