I bind the actions to ctrl-super-foo where foo is a letter associated with a mnemonic like b for browser or v for video (player). This wouldn't solve the issue of multiple windows of the same program, but I find I rarely have such a thing. On GNU/Linux with the Sway Wayland compositor, I have a bunch of keybinds to focus a program by app_id (wayland) or class (xwayland) so I can jump to specific windows even on other monitors or workspaces. The first one in particular took me a bit of time to realize before I did, it just felt broken and made me not rely on cmd+~ at all. This feels like fallout from the second point, in that if you're not showing thumbnails it could get confusing. * Cmd+~ also cycles in a static order, not most recently used. I can see why, since cmd+tab shows only icons and app names, which isn't enough to differentiate between windows of the same app (unlike alt+tab on Windows, which shows thumbnails, paths, page titles, etc. ![]() * Unlike cmd+tab, cmd+~ doesn't give me a visual overview of my windows (how many? what order?). I feel like MacOS's fullscreen paradigm is more to blame here, because it violates a range of other behaviors I'd expect. ![]() If I have fullscreen windows anywhere in my setup, it breaks my flow and (afaik) makes me mouse to the Window menu. ![]() * Cmd+~ from a fullscreen window does nothing, and non-full windows of the app cycle only among each other. ![]() It's probably a combo of my Windows background, my ignorance of MacOS tricks, and actual limitations/flaws.
0 Comments
Leave a Reply. |