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
Hello, i've been studying the tutorial on the Entering Raw Mode section specifically on Disable Ctrl-V part. I already following and typing the code carefully to be exact same as you provided in the tutorial but my terminal won't print out "22", but instead it will print out the latest copied text from my clipboard on Windows (if any, otherwise it won't print anything and stuck on the current line in the terminal).
Do you have any ideas how to fix this in WSL environment? Thanks
The text was updated successfully, but these errors were encountered:
Aiyon860
changed the title
Disabling IEXTEN won't show 22 ASCII code
Disabling IEXTEN won't show "22" ASCII code
Nov 26, 2024
Aiyon860
changed the title
Disabling IEXTEN won't show "22" ASCII code
Disabling CTRL+V by inserting IEXTEN won't show "22" ASCII code
Nov 26, 2024
Aiyon860
changed the title
Disabling CTRL+V by inserting IEXTEN won't show "22" ASCII code
Won't show "22" ASCII code after disabling CTRL+V by inserting IEXTEN
Nov 26, 2024
I was facing the same issue when using VS Code's builtin terminal. After searching the internet, I found that VS Code doesn't send ctrl + v to shell directly, instead, it sends the content of your clipboard as a sequence of key press.
If you're using VS Code, you can follow below steps to fix this issue:
Open keyboard shotcuts. (Left bottom corner icon, or ctrl + k ctrl + s)
(I'm using WSL)
Hello, i've been studying the tutorial on the Entering Raw Mode section specifically on Disable Ctrl-V part. I already following and typing the code carefully to be exact same as you provided in the tutorial but my terminal won't print out "22", but instead it will print out the latest copied text from my clipboard on Windows (if any, otherwise it won't print anything and stuck on the current line in the terminal).
Do you have any ideas how to fix this in WSL environment? Thanks
The text was updated successfully, but these errors were encountered: