When using versions of JetBrains Windows IDE's (Intellij, Goland, PyCharm, etc) that come with a new terminal implementation (Cf. this page), TCR's interactive terminal is no longer able, when running in solo mode, to handle keyboard shortcuts as expected (e.g. direct reaction to keypress without pressing the Enter key, as well as disabling keypress echo)
To Reproduce
Steps to reproduce the behavior:
Open a JetBrains Windows IDE with version 2024.1 or newer
Open a terminal (View / Tool Windows / Terminal)
Launch TCR on solo mode: tcr solo
Type one of the provided key shortcuts, for example ?
TCR displays the ? character but does not activate the related action. The user needs to type Enter in order to trigger the action
Expected behavior
TCR should trigger the action associated to the key pressed without the need to press Enter key
The shortcut action character should not be printed on the terminal
Working Environment
OS: Windows 10
JetBrains Goland 2024.1.4
TCR 1.1.0
Additional Context
After investigation, this seems to be related to JetBrain's new terminal implementation periodically resetting Windows console flags ENABLE_LINE_INPUT and ENABLE_ECHO_INPUT values (Cf. https://docs.microsoft.com/en-us/windows/console/setconsolemode) . These flags are disabled by TCR in order to get the expected behaviour in Windows terminals)
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Contact Details
damien.menanteau@gmail.com
Describe the bug
When using versions of JetBrains Windows IDE's (Intellij, Goland, PyCharm, etc) that come with a new terminal implementation (Cf. this page), TCR's interactive terminal is no longer able, when running in solo mode, to handle keyboard shortcuts as expected (e.g. direct reaction to keypress without pressing the Enter key, as well as disabling keypress echo)
To Reproduce
Steps to reproduce the behavior:
tcr solo??character but does not activate the related action. The user needs to typeEnterin order to trigger the actionExpected behavior
EnterkeyWorking Environment
Additional Context
After investigation, this seems to be related to JetBrain's new terminal implementation periodically resetting Windows console flags ENABLE_LINE_INPUT and ENABLE_ECHO_INPUT values (Cf. https://docs.microsoft.com/en-us/windows/console/setconsolemode) . These flags are disabled by TCR in order to get the expected behaviour in Windows terminals)
Code of Conduct