Visual Studio WTfs
-
@BernieTheBernie said in Visual Studio WTfs:
@dkf said in Visual Studio WTfs:
Ctrl+Shift+P
Wouldn't that send all files to the printer?
TheI hate printers
thread is !No, in Visual Stupido Code, Ctrl+Shift+P is prompt.
There is also a simpler alternative shortcut for the same thing, F1.
-
@Bulb said in Visual Studio WTfs:
There is also a simpler alternative shortcut for the same thing, F1.
TIL
-
@Bulb said in Visual Studio WTfs:
No, in Visual Stupido Code, Ctrl+Shift+P is prompt.
Ah, changing established shortcuts. Nice.
That is normally "Print Preview"There is also a simpler alternative shortcut for the same thing, F1.
And that is "Help".
-
@dcon said in Visual Studio WTfs:
@Bulb said in Visual Studio WTfs:
No, in Visual Stupido Code, Ctrl+Shift+P is prompt.
Ah, changing established shortcuts. Nice.
That is normally "Print Preview"There is also a simpler alternative shortcut for the same thing, F1.
And that is "Help".
Hence, Visual Stupido.
-
@dcon A moment of silence for those people trying to print-preview their code or trying to find help on VSC.
That came out snarkier than I intended, sorry.
-
@Zecc said in Visual Studio WTfs:
@dcon A moment of silence for those people trying to print-preview their code or trying to find help on VSC.
That came out snarkier than I intended, sorry.
They’re JavaScript developers. They don’t believe in printing because you can’t print a car from the web, and all the help they need comes from StackGPT.
-
@Zecc said in Visual Studio WTfs:
That came out snarkier than I intended
Around here, that's considered a
sorry
Level-up rescinded.
-
@dcon said in Visual Studio WTfs:
@Bulb said in Visual Studio WTfs:
No, in Visual Stupido Code, Ctrl+Shift+P is prompt.
Ah, changing established shortcuts. Nice.
That is normally "Print Preview"It's fine to have them do something else when the "normal" feature doesn't exist.
There is also a simpler alternative shortcut for the same thing, F1.
And that is "Help".
Back in the day maybe.
-
@loopback0 said in Visual Studio WTfs:
It's fine to have them do something else when the "normal" feature doesn't exist.
ď…ş I seem to be Helpless...
-
@loopback0 what’s Firefox’s excuse for making Ctrl-Shift-P into “open private window”? (I assume the answer is “print automatically has a preview window” but still.)
-
@Arantor said in Visual Studio WTfs:
@loopback0 what’s Firefox’s excuse for making Ctrl-Shift-P into “open private window”? (I assume the answer is “print automatically has a preview window” but still.)
Ctrl-Shift-Porn
-
@Applied-Mediocrity I think it goes:
Ctrl+Shift+P_or_N in Firefox_or_Chrome.
-
@dcon said in Visual Studio WTfs:
Ah, changing established shortcuts. Nice.
Speaking of which: Dear Visual Studio, Ctrl+W means "Close File", not whatever thing that might be that you seem to be trying to do whenever I hit it.
-
@ixvedeusi said in Visual Studio WTfs:
@dcon said in Visual Studio WTfs:
Ah, changing established shortcuts. Nice.
Speaking of which: Dear Visual Studio, Ctrl+W means "Close File", not whatever thing that might be that you seem to be trying to do whenever I hit it.
Perfectly cromulent behaviour. W stands for "whatever"
-
@dkf said in Visual Studio WTfs:
@Bulb said in Visual Studio WTfs:
@dkf You don't put any in comments ?
I want them in identifiers.
People of pwogwamming! Waku is your fwiend!
-
@dkf said in Visual Studio WTfs:
Minor WTF:
What is it about
va_start
that makes the highlighter do weird things with the first argument? It's a stable problem too; the rest of the file continues to be highlighted correctly as you edit things. (va_arg
andva_end
are also affected.)Looks similar to what it sometimes does with Razor markup. Most of the time, it handles it fine, but sometimes it will just completely lose all its spaghetti and the code will be rainbow clown vomit with none of the symbols being interpreted as anything related to what they actually are
-
@ixvedeusi said in Visual Studio WTfs:
Dear Visual Studio, Ctrl+W means "Close File"
But in MsPaint, it means
Open the resize dialog
.
Size matters!
-
@hungrier said in Visual Studio WTfs:
@dkf said in Visual Studio WTfs:
Minor WTF:
What is it about
va_start
that makes the highlighter do weird things with the first argument? It's a stable problem too; the rest of the file continues to be highlighted correctly as you edit things. (va_arg
andva_end
are also affected.)Looks similar to what it sometimes does with Razor markup. Most of the time, it handles it fine, but sometimes it will just completely lose all its spaghetti and the code will be rainbow clown vomit with none of the symbols being interpreted as anything related to what they actually are
Well yes, the language server can sometimes lose its mind. I was more interested in how it would consistently get things to do with the
va_
macros wrong despite clearly being still in command of what passes for its marbles (the rest of the file highlights correctly even when changed). This case is definitely something different from the usual code-no-work laugh track.I'm guessing that nobody has spotted it before because they tend to use
args
as the key variable name...