3 ms·
alt+f4, ctrl+s, ctrl+x/c/v, ctrl+z, ctrl+p all work near universally on windows. Up until Windows XP that was also true for F1, but shipping help files somehow
by wongarsu 4y ago
alt+f4, ctrl+s, ctrl+x/c/v, ctrl+z, ctrl+p all work near universally on windows. Up until Windows XP that was also true for F1, but shipping help files somehow got out of fashion. Of course there are exceptions, like conhost, but generally you don't have to think about how to save or quit something on windows
- boccaff 4y agoexcept when you have a different locale and language, and half your office suite have the original shortcuts, and the other half is translated like: ctrl + a (abrir, open in Portuguese) instead of select all, that is moved to ctrl + t (tudo, all in Portuguese), and many others. So, universally for English/US I guess.
- kergonath 4y agoMy pet peeve is ctrl+g to put some text in bold in French Office. It annoys me to no end. But then, things like ctrl-o still work as it should. Even ctrl-a, now that I think of it, and I can’t see where the a would come from.
- hulitu 4y agoYou shall see the German version. (bangs head)
- jstimpfle 4y agoYou can kill windows using alt+f4 on your typical Linux Desktop (Gnome, KDE, etc). Same for ctrl+x/c/v. It's different for programs running in terminals / terminal emulators for technical reasons. Terminals are not GUIs, they are simple devices with a single byte stream for input (displayed on screen) and output (sent from keyboard) that are interpreted quite literally. E.g. the byte ASCII 'A' will normally result in an 'A' being displayed whereever the terminal cursor happens to be. Typing 'A' on the keyboard will result in 'A' being sent out to the OS. Ctrl+(A-Z) will send the byte values 1 through 26. E.g. Ctrl+C will result in ASCII 3 (0b00000011), aka ETX (End of Text), which will normally be converted by the OS's terminal subsystem into a SIGINT signal that is sent to the "foreground" process running in the terminal. Or, if the terminal is in raw mode, the byte 3 will be read as-is by whoever reads the terminal keyboard. Same goes for ctrl+z (normally SIGSTOP is sent) etc. Terminal apps can't expect a running clipboard service. There may not be a display or graphics environment running on that machine. The app might run on remote machine. Etc. Notice how Windows Cmd isn't entirely intuitive about those basic cut&past things, either.
- vintermann 4y agoNot just those. Odds are shift+del to cut, crtl+insert to copy, shift+insert to paste still work in the browser text area you use to write comments. Even alt+backspace, the old IBM undo shortcut, still works in pretty much any box that lets you enter text in Windows. That's the power of generic UI components and backwards compatibility!
- deleted 4y ago[deleted]