I'm having a rough time trying to use VS Code on Linux. I'm trying to learn some key shortcuts, but they only seem to work half the time. When not working, they do nothing or invoke compilation. Has anyone else had anything like this experience, or am I just allergic to IDEs?
-
Show this thread
-
I guess this makes me feel more sad because everyone else I've heard from reports excellent user experience from VSCode with Metals... :'(
4 replies 0 retweets 5 likesShow this thread -
This Tweet is unavailable.
-
Replying to @wfaler
*Extensively* tested on MacOS... but they test every PR with Windows and Linux too, I believe.
1 reply 0 retweets 0 likes -
Replying to @propensive @wfaler
Might be the keys are already mapped for other Linux things? E.g I have F12 calling Guake, so “go to def” doesn’t work...
1 reply 0 retweets 1 like -
I use it on mac but have only learned two shortcuts: * Go to file * Command Palette From command palette you can type any other command like "go to definition", so that's it, I basically use it as a terminal.
1 reply 0 retweets 3 likes -
That was going to be my approach. ;)
1 reply 0 retweets 0 likes -
And is the command palette combo (assuming ctrl+shift+p in linux) not working for you?
2 replies 0 retweets 0 likes -
Just checked, and this is working, at least.
1 reply 0 retweets 1 like -
and does the rest of the integration work? Wondering about platforms; one of this days I'll need to buy a new personal computer (not company owned) and I hate the new Macbook silly bar and keyboard. Tho, I must say, my 4ish year old Macbook might outlive all the newer ones.
1 reply 0 retweets 1 like
@olafurpg kindly gave me some of his debugging time. My Unicode fonts (on Linux) weren't displaying the symbols for diagnostic output, so we were a little unsure of whether things were working, but it appeared to be more or less working. :)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.