Timeline for Windows INSERT key anti-functionality accidentally triggers; how to stop it permanently?
Current License: CC BY-SA 3.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Aug 2, 2023 at 4:49 | comment | added | skeetastax |
Num Lock is just that - it locks the numbers on. Like Scroll Lock and Caps Lock .
|
|
Apr 17, 2018 at 20:50 | comment | added | rubynorails | This is what saved me quickly without spending more time than necessary on any of the other answers. I have no Insert key and had accidentally hit the 0 on the numeric keypad. I just hit it again, and bingo-bango, the day is saved. | |
Aug 18, 2017 at 11:37 | comment | added | binaryfunt | Also make sure "Insert mode" is ticked in the Powershell settings | |
Apr 21, 2017 at 22:50 | comment | added | binaryfunt |
+1 for pressing Tab. I was wondering why overtype kept getting triggered in Powershell... It's because I press Tab all the time for autocomplete
|
|
S Jan 3, 2014 at 21:25 | history | suggested | iconoclast | CC BY-SA 3.0 |
incorporated Dennis's suggested clarification, and just generally improved style and clarity and readability
|
Jan 3, 2014 at 21:18 | review | Suggested edits | |||
S Jan 3, 2014 at 21:25 | |||||
S Jun 28, 2013 at 23:59 | history | suggested | Pecos Bill | CC BY-SA 3.0 |
Poster did not mean caps lock. It definitely should have read num lock pertaining to 0 and INS
|
Jun 28, 2013 at 23:48 | review | Suggested edits | |||
S Jun 28, 2013 at 23:59 | |||||
Aug 30, 2009 at 13:07 | comment | added | Dennis Williamson | You mean the 0-key on the numeric keypad is the insert key when num-lock is off. | |
Aug 29, 2009 at 5:25 | history | answered | user8228 | CC BY-SA 2.5 |