I needed to open the terminal in VSCode but I forgot the command — which I do all the time but by muscle memory. Thinking about it just made it harder. I had to turn my focus elsewhere and when I came back I could do it by muscle memory!
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (13)
Happens to me all the time. My keybind for opening my fuzzy finder is
<space>pf, and I've literally had to go into my config, and dig through my files until I see the binding and go "oh, yeah, that's what it was". Feels like it happens at least once a week.The same thing happens to me all the time - I can type them, but if you ask me, I won't be able to always tell what they are!
CTRL+~
It's called the tilde
For me it's
ctrl + backtick. I remember it because in markdown a code block is opened with backtick, but I cannot figure out how to escape a backtick here, so here's one in a triple backtick code block :@lolcabanon Those are both the same thing on the keyboard 😁
Not on mine! (French (Canada))
Well I learned something new today 😄
That happens to me as well and takes me a few goes to get it right.
Sort of keyboard related but I've been on macos for 6 years now and still call it the start button in my head when I am memorising chords.
I had the same problem with jibberish passwords on one of my works. I could never type them on my phone and had to use a PC to type them and see what they were. Even tho we had a 90 days change policy this happened to me every time
I have set
ctrl+Tkeybinding to open terminal. it is very handy like chrome commandsctrl+nfor new window,ctrl+rfor refreshing.So no chance of forgetting next day.
Best way if you use VSCode for code writing, and other terminal program like ghostty as terminal. Do not mix these. Terminal first development is your friend.
Seriously? Not to be a hater, but just make your own shortcut. It is so easy to do.
The real way to master your IDE is to make it your own. (See also make your own snippets)
The struggle is real! 😅 Our brains work in mysterious ways - sometimes stepping back is the best debugging technique for memory lapses